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.
git clone --depth 1 https://github.com/VaiYav/speckit-product-forgeWrote 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/commands/vaiyav/speckit-product-forge/security-check)<a href="https://agentmods.dev/commands/vaiyav/speckit-product-forge/security-check"><img src="https://agentmods.dev/badge/commands/vaiyav/speckit-product-forge/security-check.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.00073 | $0.02826 |
| Opus 5 | $0.00036 | $0.01413 |
| Sonnet 5 | $0.00015 | $0.00565 |
| Haiku 4.5 | $0.00007 | $0.00283 |
Grade A, and why
speckit.product-forge.security-check 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 8d 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Product Forge — Security Check
You are the Feature Security Auditor for Product Forge. Your goal: perform a targeted OWASP security audit scoped to exactly what this feature does — not a generic checklist, but a threat-model-driven review of the implementation.
User Input
$ARGUMENTS
Step 1: Validate Prerequisites
- Read
.forge-status.yml—implementmust becompleted - Read
plan.mdto understand what the feature does - Read
product-spec/product-spec.mdfor feature scope
Step 2: Build Feature Threat Model
Before running any checks, read plan.md and spec.md to determine which attack
surfaces are actually present. Only check what applies.
🔍 Building threat model for: {Feature Name}
Detect the following surfaces from the artifacts and code:
| Surface | Detected? | Relevant OWASP Categories |
|---|---|---|
| User authentication / login | {yes/no} | A01, A07 |
| Authorization / role checks | {yes/no} | A01, A05 |
| User-supplied input (forms, query params) | {yes/no} | A03, A06 |
| File upload / download | {yes/no} | A01, A03, A05 |
| Payment processing | {yes/no} | A02, A03, A07 |
| Third-party API calls | {yes/no} | A02, A08, A09 |
| Database queries | {yes/no} | A03 |
| Sensitive data storage | {yes/no} | A02 |
| Admin / privileged operations | {yes/no} | A01, A05 |
| Public endpoints (no auth) | {yes/no} | A05, A04 |
| External webhooks received | {yes/no} | A03, A07 |
| Cryptographic operations | {yes/no} | A02 |
| New dependencies added this feature | {yes/no} | A06, A08 |
Only perform checks for surfaces marked yes.
The New dependencies surface is yes whenever the implement phase recorded
phases.implement.dependencies.added > 0 on .forge-status.yml, or whenever
traceability.yml carries a dependencies: block (the W5-C2 dep list produced
by /speckit.product-forge.implement).
Step 3: Run Targeted Security Checks
For each detected surface, perform the following checks. Read the actual implementation files — do not guess.
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.
- 8d ago First seen · 350 lines · 73 tokens per session scan A 6c36e48a81bd
speckit.product-forge.security-check is a command published in the GitHub repository VaiYav/speckit-product-forge (23 stars, last pushed 15d ago), licensed MIT. It adds 73 tokens to every session and 2,826 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-30.
Other commands, from other repositories
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.