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 skills add lbk-open/super-spec --skill ss-show-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-show-spec)<a href="https://agentmods.dev/skills/lbk-open/super-spec/ss-show-spec"><img src="https://agentmods.dev/badge/skills/lbk-open/super-spec/ss-show-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.1 | $0.00061 | $0.00511 |
| Opus 5 | $0.00030 | $0.00255 |
| Sonnet 5 | $0.00012 | $0.00102 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
ss-show-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 6d 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
Show OpenSpec Capability
Discover and display the authoritative spec for a capability. This is the entry point for
"see what exists, then read it" — don't list or grep openspec/ blindly before calling
this skill.
Inputs
Optional: a capability name (matching a directory under openspec/specs/) or a keyword to
search for. Omit both to get an index of all capabilities.
Process
- No input given — enumerate every directory under
openspec/specs/. For each, read the## Purposesection (or the first descriptive line) of itsspec.mdand print a one-line index entry:capability-name — <purpose>. Ifopenspec/specs/is empty or missing, report that this repository has no OpenSpec baseline yet — suggest running thess-write-specorss-reverse-specskill. Stop here. - Input matches a capability directory exactly (
openspec/specs/<capability>/) — read and display thatspec.mdin full. - Input is a keyword — search every
openspec/specs/*/spec.md(and, where useful, activeopenspec/changes/*/specs/*/spec.md, excludingarchive/) for the text. Show each match with its capability name and the matching line or excerpt. If more than one capability matches, list them and ask the user which one to display in full. - After displaying a capability, list the 5 most recent archive entries that touched it —
e.g., by finding files matching
openspec/changes/archive/*/specs/<capability>/spec.mdand taking the last 5 in sorted order. For each, show the archive directory name, the first proposal heading if available, and a count of delta sections (ADDED / MODIFIED / REMOVED / RENAMED).
Output
Keep the surrounding commentary concise, but always include the full current spec text. 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.
- 6d ago First seen · 40 lines · 61 tokens per session scan A 98335c37bfaa
ss-show-spec is a skill published in the GitHub repository lbk-open/super-spec (1 stars, last pushed 15d ago), licensed Apache-2.0. It adds 61 tokens to every session and 511 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.
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.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.