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 takaoumehara/superforge-skill --skill superforge-securegit clone --depth 1 https://github.com/takaoumehara/superforge-skillWrote 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/takaoumehara/superforge-skill/superforge-secure)<a href="https://agentmods.dev/skills/takaoumehara/superforge-skill/superforge-secure"><img src="https://agentmods.dev/badge/skills/takaoumehara/superforge-skill/superforge-secure.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.00214 | $0.02397 |
| Opus 5 | $0.00107 | $0.01198 |
| Sonnet 5 | $0.00043 | $0.00479 |
| Haiku 4.5 | $0.00021 | $0.00240 |
Grade A, and why
superforge-secure 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 7d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Superforge Secure — Security Review for Products Without a Security Team
Security is not a scanner score, and it is not a topic for later. A product can pass every automated check, have no known CVE, and still let any logged-in user read every other user's data by changing a number in a URL.
This skill runs the passes a machine cannot run, ranks findings by what an
attacker gets, and writes a ledger that superforge-ship reads before a
release.
0. The rule this skill exists to enforce
Never report that something is secure. Report what was checked.
"Secure" is not a state a review can establish — it is the absence of every unknown flaw, which no process can demonstrate. A review can only say: these seven passes were run against this surface on this date, and here is what they found and what they did not cover.
This is the same discipline as superforge-verify, applied to a domain where
the false clearance is more expensive: a user who is told "we checked, it's
secure" stops looking.
Two corollaries:
- A clean dependency scan is the start of the review. It sees published vulnerabilities in third-party code and is blind to every flaw in yours, which is where the findings in §2's passes 1–3 actually live.
- Report
SECURE-REVIEWED/FINDINGS-OPEN/NOT-ASSESSED, never "secure".
1. Scope before reviewing
Four things, written at the top of the report. Guess the defaults and confirm rather than interrogating.
| Default if unstated | |
|---|---|
| Surface | every route or screen that touches data, plus every background job and third-party webhook |
| Trust boundary | anything the client sends is attacker-controlled — including headers, IDs, prices, and any value your own JavaScript put there |
| Attacker model | a logged-in ordinary user of your product. Not a nation state. This is the one that finds real bugs at this scale |
| Blast radius | what the worst single compromise reaches — one account, all accounts, the database, the payment provider |
What ships with it
9 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.
- 7d ago First seen · 212 lines · 214 tokens per session scan A 3cade89b828f
superforge-secure is a skill published in the GitHub repository takaoumehara/superforge-skill (1 stars, last pushed 22d ago), licensed MIT. It adds 214 tokens to every session and 2,397 once invoked, about $0.0011 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
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
mongodb-query-optimizer
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query…
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.
neo4j-modeling-skill
Design, review, and refactor Neo4j graph data models. Use when choosing node labels vs relationship types vs properties, migrating relational/document schemas to graph, detecting anti-patterns (generic labels, supernodes, missing constraints), designing intermediate nodes for n-ary relationships, enforcing schema with…
lov-article-creator
A skill that turns source material or a draft into a complete, branded WeChat public-account article package.
lov-repo2docs
Turn any folder of source material — a code repository, a pile of articles, a mixed knowledge dump with images — into a professional, polished Fumadocs (Next.js) documentation website, then deploy it to https://{product-id}.example.com/docs. Works by reading the folder one unit at a time and incrementally growing and…