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/Mininglamp-OSS/octo-specWrote 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/mininglamp-oss/octo-spec/octospec-plan)<a href="https://agentmods.dev/commands/mininglamp-oss/octo-spec/octospec-plan"><img src="https://agentmods.dev/badge/commands/mininglamp-oss/octo-spec/octospec-plan/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/mininglamp-oss/octo-spec/octospec-plan"><img src="https://agentmods.dev/badge/commands/mininglamp-oss/octo-spec/octospec-plan.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.00021 | $0.00282 |
| Opus 5 | $0.00010 | $0.00141 |
| Sonnet 5 | $0.00004 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
octospec-plan 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 11d 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.
This is a copy
100% identical to octospec-plan — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are running the octospec Plan phase for this repo.
Task: $ARGUMENTS
- Pick a short kebab-case
<slug>for this task. - Read
.octospec/tasks/_brief.template.mdfor the required shape. - Inspect the relevant existing code to ground the brief in reality (you may draft the brief from the code; the human will confirm it).
- Write
.octospec/tasks/<slug>/brief.mdfilling every section (including the OKF frontmatter from the template — settype: Task,title,description,tags,timestamp):- Goal — what behavior changes and why.
- Load-bearing list — existing behaviors/contracts this touches. Use the
same tags as
.octospec/rules/_index.yamlinject_when.toucheswhere they apply, so the right rules get injected later. - Out of scope — what this deliberately does NOT touch.
- Acceptance — machine-checkable where possible.
- Do NOT write implementation code in this phase. Stop after the brief and show it for confirmation.
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.
- 11d ago First seen · 25 lines · 21 tokens per session scan A 783d0c922b7f
octospec-plan is a command published in the GitHub repository Mininglamp-OSS/octo-spec (19 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 282 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to octospec-plan, differing in 0 lines, and is treated as a copy.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.