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 skills/lbk-open/super-spec/ss-trace-specnpx skills add lbk-open/super-spec --skill ss-trace-specgit clone --depth 1 https://github.com/lbk-open/super-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/skills/lbk-open/super-spec/ss-trace-spec)<a href="https://agentmods.dev/skills/lbk-open/super-spec/ss-trace-spec"><img src="https://agentmods.dev/badge/skills/lbk-open/super-spec/ss-trace-spec.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.00054 | $0.00300 |
| Opus 5 | $0.00027 | $0.00150 |
| Sonnet 5 | $0.00011 | $0.00060 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
ss-trace-spec 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
Trace OpenSpec History
Reconstruct the history of a Requirement or Scenario by searching current specs and archived deltas.
Inputs
Required: the requirement or scenario text (or a close paraphrase) to trace.
Process
- Search current specs for the query text, e.g., using your repository search tool over
openspec/specs. - Search archived deltas for the same query over
openspec/changes/archive. - For each archive hit, read the surrounding context:
- the archive directory name
- which delta section it appeared in (ADDED / MODIFIED / REMOVED / RENAMED)
- the Requirement heading
- the proposal heading or summary, if present
- If the project is under git, also pull the source-of-truth file history, e.g.
git log --oneline -- openspec/specs.
Output
Return a chronological summary covering:
- where the behavior currently lives
- which archived changes touched it, in order
- whether each touch added, modified, removed, or renamed it
- file paths worth reading next
Do not edit any files.
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 · 38 lines · 54 tokens per session scan A 4c1e2041f0dd
ss-trace-spec is a skill published in the GitHub repository lbk-open/super-spec (1 stars, last pushed 13d ago), licensed Apache-2.0. It adds 54 tokens to every session and 300 once invoked, about $0.0003 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 skills, from other repositories
phx-deps-audit
Audit Hex deps for supply-chain security risk — bidi chars, compile-time exec, maintainer changes, typosquats, CVEs. Use after mix deps.update, when checking if a package upgrade is safe, or reviewing mix.lock PR diffs.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.