Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add orin-dx/agent-plugins --skill correct-specgit clone --depth 1 https://github.com/orin-dx/agent-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/orin-dx/agent-plugins/correct-spec)<a href="https://agentmods.dev/skills/orin-dx/agent-plugins/correct-spec"><img src="https://agentmods.dev/badge/skills/orin-dx/agent-plugins/correct-spec.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00034 | $0.00430 |
| Opus 5 | $0.00017 | $0.00215 |
| Sonnet 5 | $0.00007 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
correct-spec scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Correct a contradictory specification
Outcome
Revise only the affected criteria and dependent plan implications while preserving the spec identity, durable path, and audit trail.
Workflow
- Read the spec from its
spec_file_path; validate it usingshared/schemas/[email protected]. - Inspect the contradiction report and live workspace behavior. Confirm that the conflict is real rather than a missing implementation step or a misunderstood test.
- Identify the affected criterion and dependent criteria. Amend only the necessary text, set
revision_note, and retain the same spec ID and file path. - Run the corrected draft through
scribe:verify-spec,scribe:audit-spec,scribe:audit-architecture, andscribe:gate-spec. - After a passing gate and user authorization, overwrite the existing
docs/specs/<id>.jsonartifact, commit it, and send its changed criterion IDs tonavigator:planin amend mode.
Contract
- Input schema:
shared/schemas/[email protected] - Output schema:
shared/schemas/[email protected] - Durable path: the existing
spec_file_path, normallydocs/specs/<id>.json - Follow-on: amended
shared/schemas/[email protected]must go through planning review before implementation resumes.
Teams and fallback
Before delegating, read agent-roles/README.md; use tracer only for independent contradictory paths and keep the correction itself with the primary author.
This is a narrow evidence-and-judgment task; work alone by default. Use a teammate only when the contradiction spans independent code paths, and reconcile evidence before editing the spec.
Boundaries
- Do not correct the spec for the same criterion twice without escalating to the user.
- Do not overwrite the persisted file or commit without user authorization.
- Do not continue implementation against a criterion confirmed to be contradictory.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- today Changed · +2 lines · -70 tokens per session 3bdf6e3a150c
- 6d ago First seen · 36 lines · 104 tokens per session scan A 7160f92f63f9
correct-spec is a skill published in the GitHub repository orin-dx/agent-plugins (1 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 430 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
accessibility-tester
Professional Accessibility Tester Expert skill. Implement robust test suites and automated quality checks for modern web/mobile applications.
bdd-cucumber
Professional BDD Cucumber Expert skill. Implement robust test suites and automated quality checks for modern web/mobile applications.
flaky-test-fixer
Professional Flaky Test Fixer Expert skill. Implement robust test suites and automated quality checks for modern web/mobile applications.
integration-tester
Professional Integration Tester Expert skill. Implement robust test suites and automated quality checks for modern web/mobile applications.
load-tester
Professional Load Tester Expert skill. Implement robust test suites and automated quality checks for modern web/mobile applications.
mock-master
Professional Mock Master skill. Implement robust test suites and automated quality checks for modern web/mobile applications.