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/asasugar/superspec/ss-linkgit clone --depth 1 https://github.com/asasugar/SuperSpecWrote 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/asasugar/superspec/ss-link)<a href="https://agentmods.dev/commands/asasugar/superspec/ss-link"><img src="https://agentmods.dev/badge/commands/asasugar/superspec/ss-link.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.00007 | $0.00198 |
| Opus 5 | $0.00003 | $0.00099 |
| Sonnet 5 | $0.00001 | $0.00040 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
/ss-link 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
Input Parsing Rules
From user input, extract: change name, dependency target.
| Extract | Rule | Example |
|---|---|---|
| Change name | First argument or text before --on |
/ss-link addAuth --on addDB → name=addAuth |
| Dependency target | --on <other>/depends on <other>/→ <other> → extract target name |
/ss-link addAuth --on addDB; /ss-link addAuth depends on addDB |
Steps
- Parse user input → extract change name and dependency target
- Run
superspec deps add <name> --on <other> - Verify:
superspec deps list <name>
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 · 22 lines · 7 tokens per session scan A 6320fa402164
/ss-link is a command published in the GitHub repository asasugar/SuperSpec (15 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 198 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-30.
Other commands, from other repositories
codebase-audit
Survey a codebase as a senior advisor and produce prioritized, self-contained improvement plans. Read-only on source code. Use standalone before iteration-start to discover what's worth doing, or independently to build a prioritized backlog.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Bulk Archive
Archive multiple completed changes at once.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
OPSX: New
Start a new change using the experimental artifact workflow (OPSX).