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-create-prnpx skills add lbk-open/super-spec --skill ss-create-prgit 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-create-pr)<a href="https://agentmods.dev/skills/lbk-open/super-spec/ss-create-pr"><img src="https://agentmods.dev/badge/skills/lbk-open/super-spec/ss-create-pr.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.00113 | $0.03360 |
| Opus 5 | $0.00056 | $0.01680 |
| Sonnet 5 | $0.00023 | $0.00672 |
| Haiku 4.5 | $0.00011 | $0.00336 |
Grade A, and why
ss-create-pr 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Pull/Merge Request
Finalize development work once coding and review are done: run pre-flight checks, clean up, rebase, and open a PR/MR — or, if that's not possible, land the work with a clean conventional-commit history and a written summary instead.
Core principle: archive specs → verify → clean → rebase → verify again → ship. Never open a PR/MR with failing tests, debug artifacts, unresolved conflicts, or an unarchived delta spec. Avoid redundant test runs — if a prior coding step already verified tests at the current commit, trust that result.
This is the last step of a development workflow. It assumes implementation is complete (e.g., via the ss-coding skill or manual work) and review is done (e.g., via the ss-code-review skill or manual review), with all review issues addressed.
Inputs
- Target branch (optional — defaults to the remote's detected default branch).
--draftto open the PR/MR as a draft.- Delivery mode, if this skill is running standalone rather than as part of a larger workflow: full (the normal case — this skill actually opens a PR/MR) or lite (the calling workflow already decided to skip PR creation and land changes locally; if so, skip straight to "Local fallback" below).
Ground rules
- Tests must pass before opening a PR/MR. If they haven't been verified at the current commit, run them; if they fail, stop and fix first. Don't re-run tests already verified at the same commit.
- No debug artifacts — stray
console.log, debugger statements, TODO/HACK markers, disabled test selectors, secrets — must be removed first. - Rebase, never merge the target branch into the feature branch.
- Verify again after rebase only if the rebase actually changed code. A no-op rebase (already up to date) needs no re-verification.
- Never force-push without explicit consent. A first-time push never needs force.
- The PR/MR description must be substantive — auto-generate one from the commit history if the user doesn't supply one.
- Archive any active delta spec first — run the
ss-archiveskill; it's idempotent and no-ops when there's no active delta.
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 · 257 lines · 113 tokens per session scan A 50e8ccdc3f3e
ss-create-pr is a skill published in the GitHub repository lbk-open/super-spec (1 stars, last pushed 12d ago), licensed Apache-2.0. It adds 113 tokens to every session and 3,360 once invoked, about $0.0006 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.