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/ethandev147/specrossWrote 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/ethandev147/specross/help)<a href="https://agentmods.dev/commands/ethandev147/specross/help"><img src="https://agentmods.dev/badge/commands/ethandev147/specross/help/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/ethandev147/specross/help"><img src="https://agentmods.dev/badge/commands/ethandev147/specross/help.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.00000 | $0.00372 |
| Opus 5.5 | $0.00000 | $0.00149 |
| Sonnet 5.5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
help 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 1mo 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
Print the Specross command reference. No arguments needed.
Print the following help text exactly:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
⚡ SPECROSS — Spec-driven development (SDD)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
BA ────────────────────────────────────────────────────
/ba:new-story {story} Create story, ask clarifying questions
/ba:review {story} Check for gaps before releasing
/ba:impact {story} Preview Dev/QC impact of pending changes
/ba:release {story} {version} Promote to stories/, write release note
DEV ────────────────────────────────────────────────────
/dev:gen-tech-spec {story} story → tech-spec + API files + tasks
/dev:implement {story} {task-id} Implement a task against the spec
/dev:review {story} Check implementation vs AC
/dev:sync {story} Spec updated? Diff what needs changing
/dev:done {story} Mark complete, write handoff for QC
QC ────────────────────────────────────────────────────
/qc:gen-test-cases {story} story → test cases organized by AC
/qc:run {story} [TC-ID] Run TCs interactively — auto bug report on fail, auto-close on retest pass
/qc:sync {story} Spec updated? Update affected test cases
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
BA: new-story → review → release
Dev: gen-tech-spec → implement → review → done
QC: gen-test-cases → run (retest bằng /qc:run {story} {TC-ID})
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
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.
- 1mo ago First seen · 36 lines · 0 tokens per session scan A 021c36fb80bb
help is a command published in the GitHub repository ethandev147/specross (8 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 372 tokens. 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
archive
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
OPSX: Verify
Verify implementation matches change artifacts before archiving.
opsx-propose
Propose a new change - create it and generate all artifacts in one step.
opsx-ff
Create a change and generate all artifacts needed for implementation in one go.
opsx-continue
Continue working on a change - create the next artifact (Experimental).