Write the Acceptance Test Into Your AI Agent's Spec
A green build proves the code compiled. It says nothing about whether the work is correct. Write the acceptance test into the spec, then measure how well it survives an agent gaming its own grade.
12 posts tagged #slash-commands.
A green build proves the code compiled. It says nothing about whether the work is correct. Write the acceptance test into the spec, then measure how well it survives an agent gaming its own grade.
Agent-driven file discovery burns 12,000 tokens rediscovering three files you already knew. A parameterized priming command drops that to 6,200, and the saving holds from session one.
A single root rules file guarantees every convention is always present for every edit - which is exactly what floods a backend edit with frontend rules it will never use. The fix is directory-scoped files, and the tax has a number: 62.5%.
The MCP spec hands a server three levers: resources for the application, tools for the model, prompts for the user. Skip that sort and your reads ride the tool list every turn, at a price you can compute.
Ask an agent to grade the work you just described and it grades the paragraph, not the code, because agreeing with a confident claim is the model's strongest reflex. Hand the same model the live diff and a rubric you author, and it finds the four misses your summary hid.
A one-line bug report about an agent carries exactly one testable fact: how often the failure fires. Turn the report into a committed synthetic scenario, then let that fact size how many reruns a fixed verdict is worth.
The correction you keep re-typing into the chat is a workflow you haven't written down. Priced with a small invented schedule, it costs about 43 silently skipped build gates a quarter. Encoded as a slash command, it costs zero.
When the window fills, auto-compaction writes a faithful summary and a handoff file writes an edited one. Both can be 200 tokens; next session they are 5,000 tokens apart, and the whole gap is one line saying what was ruled out.
The triage prompt your team keeps re-typing makes the agent reassemble, through three round trips, context one expert already knew how to assemble once. That costs 600 plumbing tokens and 7.2 seconds per run. A server-side MCP prompt pays the assembly once, for everybody.
Your local review habit and your CI gate are two implementations of one question, and nothing forces them to agree. Write the policy once, pin the context, and both surfaces run literally the same check for about two cents a call. The same 30 weekly pull requests on Anthropic's managed Code Review run $450 to $750.
A rules file is right the day you write it and silently wrong forever after, because nothing marks a reversed line. Auto-memory keeps both truths and cannot pick one. A trigger, a dated demotion, and a human gate end it.
Progressive disclosure keeps a skill library's index cost linear. The number of skill pairs an agent can confuse grows with the square of the library size - and nothing about a growing index tells you that's happening.