Skip to content
SkillMixed4,346 tokens in use

Agent Instructions

Write and maintain the AGENTS.md or CLAUDE.md every session reads, so each rule is met at the moment it applies.

680 stars on the repository MIT Licensephuryn/product-engineering · agent-harness/skills/agent-instructions
npx skills add phuryn/product-engineering
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Agent Instructions costs

42tokens idle
4,346tokens in use
17,221tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Mixed

Script-ledMixedModel-led

Scripts do part of the work and the model's judgement does the rest.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: scripts/check_budgets.py, scripts/check_reachable.py.

Touches

shelldetectedwrites filesdetectedgitdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter8/15
  • Structure25/25
  • Examples12/15
  • Output15/15
  • Size13/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 180
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 180

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance100
  • Community44
  • Maturity4
  • Momentum40

Agent Instructions is a skill for writing or restructuring an app repository’s entry file, adding a rule when you say “remember this”, and fixing the file after an agent ignored a rule it had. It treats the entry file as a router: a short file that points to operative files by the task the agent is doing.

It also keeps the file healthy over time. Every rule carries a dated receipt, files have word budgets held by a script, and two passes (at each release and after each mistake) keep it from growing into a manual.

What You Get

  • A starter AGENTS.md skeleton with a preamble, a router and a product section
  • A router pattern with rows worded the way a user would say the task
  • Two scripts: one lists docs no chain from the entry file reaches, one checks word budgets and rules past their review date
  • Working rules for the file, each with a receipt in a separate receipts file
  • A release pass and a mistake pass for keeping the file current

Common Use Cases

  • Creating the first AGENTS.md for a new repository
  • Restructuring a bloated CLAUDE.md into a router with area files
  • Turning a corrected mistake into a dated rule, or into a test or script when memory would fail
  • Checking that Claude Code and Codex both read the same master instruction file

What Makes It Unique

Most guidance on instruction files lists rules to include. This skill is about when a rule reaches the agent: router rows keyed by moment, a cap on always-on rules, a word budget per file, and the test of asking a fresh session to quote a rule only the file holds. A rule that depends on memory at a decisive moment is turned into a script, test or required argument. Every rule keeps the date and the failure that taught it.

Under The Hood

The skill is mostly instructions the model reads, with five reference files and a receipts file loaded on demand. It ships two Python scripts that use only the standard library and read the repository without writing anything: one walks the links from the entry files to find unreachable docs, the other counts words per file against a budgets file. The agent runs them with shell commands and edits the repository’s instruction files and docs. It fetches no web pages and calls no APIs.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers