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/terry-mao/aicodingflow/security-review-specnpx skills add Terry-Mao/AICodingFlow --skill security-review-specgit clone --depth 1 https://github.com/Terry-Mao/AICodingFlowWrote 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/terry-mao/aicodingflow/security-review-spec)<a href="https://agentmods.dev/skills/terry-mao/aicodingflow/security-review-spec"><img src="https://agentmods.dev/badge/skills/terry-mao/aicodingflow/security-review-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.00081 | $0.00874 |
| Opus 5 | $0.00041 | $0.00437 |
| Sonnet 5 | $0.00016 | $0.00175 |
| Haiku 4.5 | $0.00008 | $0.00087 |
Grade A, and why
security-review-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 5d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review Spec Skill
Audit the current spec pull request for design-level security concerns and fold
any findings into the same review.json produced by review-spec.
Required Contract
Read .agents/contracts/review.md and follow it exactly. This skill is a
supplement to review-spec; it must not create a separate report, change the
review.json schema, loosen diff-line targeting, post to GitHub, perform
code-level review, or regenerate snapshots.
When To Apply
- Apply on spec PRs whenever
review-specis applied. - Do not apply on code PRs handled by
review-pr. - Skip the skill when the changed spec content has no plausible security surface, such as purely editorial wording, typo fixes, or doc structure cleanup.
- Do not duplicate findings the base
review-specpass will already raise.
Security Concerns
Evaluate changed spec content at the design-doc level. Focus on gaps or ambiguities that would plausibly lead to an insecure implementation.
Threat Surface And Trust Boundaries
- New external inputs, endpoints, webhooks, CLI surfaces, or file formats without clear reachability and trust assumptions.
- User-supplied or third-party content flowing into automation, prompts, commands, or storage without a validation or sanitization plan.
- Features that expand what unauthenticated or low-privilege actors can cause the system to do.
- Agent or LLM-driven flows where untrusted input can be interpreted as instructions without a mitigation.
Authentication And Authorization
- New actors, roles, automation identities, or triggers without clear authentication and authorization rules.
- Informal enforcement language such as "only maintainers can trigger this" without saying how the workflow enforces it.
- Privilege escalation where a less-privileged actor can cause a more-privileged bot, workflow, or agent to act on their behalf.
Sensitive Data, Secrets, And Privacy
- New data collection, storage, logging, or transmission without sensitivity, retention, or access-control expectations.
- Private repository contents, personal data, auth tokens, session identifiers, or customer data routed through logs, prompts, or third-party services without a redaction plan.
- New credentials, API keys, signing keys, or tokens without storage, access, rotation, and leak-response expectations.
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.
- 5d ago First seen · 92 lines · 81 tokens per session scan A 2916d7bf6806
security-review-spec is a skill published in the GitHub repository Terry-Mao/AICodingFlow (165 stars, last pushed 7d ago), licensed MIT. It adds 81 tokens to every session and 874 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…