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-referencesnpx skills add lbk-open/super-spec --skill ss-referencesgit 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-references)<a href="https://agentmods.dev/skills/lbk-open/super-spec/ss-references"><img src="https://agentmods.dev/badge/skills/lbk-open/super-spec/ss-references.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.00080 | $0.00470 |
| Opus 5 | $0.00040 | $0.00235 |
| Sonnet 5 | $0.00016 | $0.00094 |
| Haiku 4.5 | $0.00008 | $0.00047 |
Grade A, and why
ss-references 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 3d 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
Shared References
This skill is a template library, not a workflow. It has no standalone "run" behavior. Other skills read one of the files below at the exact point where they need to dispatch a subagent, generate an artifact, or make a routing decision.
What's Here
| File | Covers | Read When |
|---|---|---|
implementer-prompt.md |
The dispatch prompt shape for implementer subagents | Before dispatching an implementer (ss-coding) |
proposal-template.md |
Section-by-section structure of a technical proposal | Before writing a proposal (ss-proposal) |
proposal-writing.md |
Quality-standards checklist a proposal must pass | During a proposal's self-review (ss-proposal) |
openspec-skeleton.md |
The openspec/ directory skeleton for a project that has none |
Before writing specs into a project without an openspec/ tree (ss-write-spec, ss-reverse-spec) |
multi-repo-detection.md |
Rules for deciding whether a requirement spans repositories | At a workflow's entrance, and after a proposal records its repository list |
How Other Skills Reach It
Skills reference these files by sibling relative path — ../ss-references/<file>.md
— which resolves both in this repository and after an install flattens every skill
directory into the same parent (~/.agents/skills/). This directory is a skill, and
not a bare folder, precisely so that installers carry it along: the skills CLI only
copies directories that contain a SKILL.md.
Because of that, the skills here must be installed as a bundle. Installing a single
skill on its own (for example --skill ss-coding) leaves its ../ss-references/…
reads dangling.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 33 lines · 80 tokens per session scan A 9fc728922b01
ss-references is a skill published in the GitHub repository lbk-open/super-spec (1 stars, last pushed 12d ago), licensed Apache-2.0. It adds 80 tokens to every session and 470 once invoked, about $0.0004 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
amazon-reviews-api-skill
This skill helps users automatically extract Amazon product reviews via the Amazon Reviews API. Agent should proactively apply this skill when users express needs like getting reviews for Amazon product with ASIN B07TS6R1SF, analyzing customer feedback for a specific Amazon item, getting ratings and comments for a…
amazon-competitor-analyzer
Scrapes Amazon product data from ASINs using browseract.com automation API and performs surgical competitive analysis. Compares specifications, pricing, review quality, and visual strategies to identify competitor moats and vulnerabilities.
muapi-media-editing
Edit and enhance images and videos with AI via muapi.ai — prompt-based editing, upscaling, background removal, face swap, lipsync, video effects, and more.
ctf-malware
Provides malware analysis and network traffic techniques for CTF challenges. Use when analyzing obfuscated scripts, malicious packages, custom crypto protocols, C2 traffic, PE/.NET binaries, RC4/AES encrypted communications, YARA rules, shellcode analysis, memory forensics for malware (Volatility malfind, process…
research
Conduct preliminary research on a topic and generate research outline. For academic research, benchmark research, technology selection, etc.
ecommerce-landing-page
Audit and optimize e-commerce landing pages for conversion. CTA placement, trust signals, page structure, copy optimization, and A/B testing strategy for product pages, collection pages, and campaign landing pages.