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.
git clone --depth 1 https://github.com/sorah/configWrote 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/commands/sorah/config/implement)<a href="https://agentmods.dev/commands/sorah/config/implement"><img src="https://agentmods.dev/badge/commands/sorah/config/implement/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/sorah/config/implement"><img src="https://agentmods.dev/badge/commands/sorah/config/implement.svg" alt="Reviewed on agentmods" width="80" 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.00018 | $0.00924 |
| Opus 5.5 | $0.00007 | $0.00370 |
| Sonnet 5.5 | $0.00004 | $0.00185 |
| Haiku 4.5 | $0.00002 | $0.00092 |
Grade A, and why
implement 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement a feature based on a well-defined spec file. The spec is the single source of truth — follow it precisely. Work through deliverables methodically, updating the spec's Current Status section after completing each task.
Input
The user provides a spec file path as argument: $ARGUMENTS
If no argument is given, ask the user which spec file to implement.
Preparation Phase
Before writing any code:
- Read the spec file thoroughly — understand the full design before starting
- Read all referenced files — schema files, existing code, related specs mentioned in the spec
- Read project conventions — check for project-level documentation (CLAUDE.md, style guides, architecture docs, knowledge files) relevant to the spec's domain. Project-specific conventions and framework-specific skills always take priority over general approaches
- Explore existing codebase for related models, modules, patterns, and conventions that the implementation must follow or integrate with
- Verify the spec is implementation-ready — check that the Current Status section indicates the interview is complete and a checklist exists. If the spec still contains unresolved TODOs, ambiguous language ("TBD", "maybe", "possibly"), or lacks a checklist, stop and inform the user that the spec needs further review before implementation
Initializing Current Status
If the spec's Current Status section is still in interview format (no checklist), convert it to the implementation format before starting work:
## Current Status
Implementation in progress. Implementors MUST keep this section updated as they work.
### Checklist
- [ ] First deliverable
- [ ] Second deliverable
...
### Updates
(No updates yet)
Derive checklist items from the spec's deliverables section. Each item should be a concrete, completable task.
Implementation Phase
Work through the checklist items in a logical order — respect dependencies between items (e.g., migrations before models, models before services, services before API endpoints).
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.
- yesterday First seen · 77 lines · 18 tokens per session scan A a8c071ff2735
implement is a command published in the GitHub repository sorah/config (31 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 924 once invoked, about $0.0001 per session on Opus 5.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-10-17.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.