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-reverse-specnpx skills add lbk-open/super-spec --skill ss-reverse-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-reverse-spec)<a href="https://agentmods.dev/skills/lbk-open/super-spec/ss-reverse-spec"><img src="https://agentmods.dev/badge/skills/lbk-open/super-spec/ss-reverse-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.00077 | $0.00842 |
| Opus 5 | $0.00039 | $0.00421 |
| Sonnet 5 | $0.00015 | $0.00168 |
| Haiku 4.5 | $0.00008 | $0.00084 |
Grade A, and why
ss-reverse-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 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.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reverse OpenSpec Baseline
Generate source-of-truth specs under openspec/specs/ from existing code. This is how a
brownfield repository gets a meaningful capability snapshot instead of starting from an
empty openspec/specs/ directory.
Inputs
One of:
--baseline— scan the whole repository and generate specs for every capability found- a single capability name — generate or update just that one spec
Optional: --include <path> / --exclude <path> to scope the scan.
Step 0: Ensure the OpenSpec Skeleton Exists
Check whether openspec/specs/ and openspec/changes/ already exist. If this repository
has no OpenSpec structure yet, create it first by following
../ss-references/openspec-skeleton.md, then continue below. If the skeleton already
exists, skip straight to the requested mode.
Modes
| Mode | Trigger | Output |
|---|---|---|
| Baseline | --baseline |
scan the repo, generate specs for every capability found |
| Single capability | a capability name | generate or update one capability spec |
Process: Baseline Mode
Step 1: Discover Capability Candidates
Collect signals from:
README.md, an application-overview doc, anddocs/- controller / handler / route files
- service / domain layer names
- OpenAPI paths
- database migration or DDL table names
Cluster the candidates into kebab-case business noun phrases. For each candidate, list the evidence files that back it.
Step 2: User Confirmation Gate
Show the candidate list with evidence and ask the user to confirm merges, splits, renames, or removals. Do not generate baseline specs until capability ownership is confirmed.
Step 3: Reverse-Engineer Requirements
For each confirmed capability, inspect only the relevant files:
- public API / controller / handler behavior
- service or domain behavior
- DTO / schema validation
- error handling visible to callers
- relevant tests
Write observable behavior only. Do not include implementation details — cache choice, table names, internal algorithms — unless callers can actually observe them.
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 · 124 lines · 77 tokens per session scan A 62b94fedcb56
ss-reverse-spec is a skill published in the GitHub repository lbk-open/super-spec (1 stars, last pushed 12d ago), licensed Apache-2.0. It adds 77 tokens to every session and 842 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.