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 agentmods add commands/orlando-japan/claude-code-setting/spec-applygit clone --depth 1 https://github.com/orlando-japan/claude-code-settingWrote 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/orlando-japan/claude-code-setting/spec-apply)<a href="https://agentmods.dev/commands/orlando-japan/claude-code-setting/spec-apply"><img src="https://agentmods.dev/badge/commands/orlando-japan/claude-code-setting/spec-apply.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 | $0.00009 | $0.00250 |
| Opus 5 | $0.00005 | $0.00125 |
| Sonnet 5 | $0.00002 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
spec-apply 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 4d ago.
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
Execute the implementation tasks from the spec change folder: $ARGUMENTS (or the most recently modified folder under openspec/changes/ if no argument).
Rules:
- Work tasks in the order listed in
tasks.md. - For each task: read its verification line first. Know what "done" means before you start.
- Run the verification immediately after implementing. Don't batch and verify at the end.
- Check off tasks in
tasks.mdas they complete — edit the file, don't just claim it in chat. - If a task reveals the spec is wrong, stop. Don't silently fix the spec. Surface the discrepancy to the user and ask whether to update the spec before continuing.
- Follow the four coding principles (think first, simple, surgical, goal-driven). Don't expand scope beyond what tasks specify.
- Commit per logical task group, not per file. Reference the change slug in the commit message.
When all tasks are checked, run the full test suite and report. Don't run /spec:archive yourself — the user does that after review.
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.
- 4d ago First seen · 19 lines · 9 tokens per session scan A 9796eb9b16e4
spec-apply is a command published in the GitHub repository orlando-japan/claude-code-setting (2 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 250 once invoked, about $0.0000 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
clarify
Walk through inbox items applying the GTD decision tree. Usage: /gtd:clarify [--id gtd-xxx].