Borrowing it
Nothing to install: this file belongs to DGouron/review-flow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DGouron/review-flow/master/.claude/skills/security/SKILL.mdgit clone --depth 1 https://github.com/DGouron/review-flowWrote 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/dgouron/review-flow/security)<a href="https://agentmods.dev/skills/dgouron/review-flow/security"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/security/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dgouron/review-flow/security"><img src="https://agentmods.dev/badge/skills/dgouron/review-flow/security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.01004 |
| Opus 5.5 | $0.00014 | $0.00402 |
| Sonnet 5.5 | $0.00007 | $0.00201 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
security 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 2mo 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security - Secret Detection
Persona
Read .claude/roles/code-reviewer.md — adopt this profile and follow all its rules.
Activation
This skill activates:
- Before a
git commitorgit push - On explicit request (
/security) - Via the CLI command
flux security-scan(full repo scan)
Detected Patterns
Tokens & API Keys
| Pattern | Example | Regex |
|---|---|---|
| GitLab PAT | glpat-xxxx |
glpat-[a-zA-Z0-9_-]{20,} |
| GitHub PAT | ghp_xxxx |
gh[ps]_[a-zA-Z0-9]{36,} |
| GitHub OAuth | gho_xxxx |
gho_[a-zA-Z0-9]{36,} |
| OpenAI | sk-xxxx |
sk-[a-zA-Z0-9]{32,} |
| Anthropic | sk-ant-xxxx |
sk-ant-[a-zA-Z0-9-]{32,} |
| AWS Access Key | AKIA... |
AKIA[0-9A-Z]{16} |
| AWS Secret | - | [a-zA-Z0-9/+=]{40} (AWS context) |
| Slack Token | xox[baprs]- |
xox[baprs]-[a-zA-Z0-9-]+ |
| Discord Token | - | [MN][a-zA-Z0-9]{23,}\.[a-zA-Z0-9-_]{6}\.[a-zA-Z0-9-_]{27} |
Generic Credentials
| Pattern | Context |
|---|---|
password\s*=\s*["'][^"']+["'] |
Hardcoded passwords |
secret\s*=\s*["'][^"']+["'] |
Hardcoded secrets |
token\s*=\s*["'][^"']+["'] |
Hardcoded tokens |
api[_-]?key\s*=\s*["'][^"']+["'] |
Hardcoded API keys |
Bearer [a-zA-Z0-9_-]+\.[a-zA-Z0-9_-]+\.[a-zA-Z0-9_-]+ |
JWT tokens |
Suspicious Files
| File | Risk |
|---|---|
.env |
Environment variables (often secrets) |
*.pem, *.key |
Private keys |
secrets.*, credentials.* |
Secret files |
config.toml with [secrets] section |
Config with embedded secrets |
id_rsa, id_ed25519 |
Private SSH keys |
Workflow
Pre-commit scan (git diff --staged)
SECURITY - Pre-commit Scan
Analyzing staged diff...
Result:
- Files scanned: X
- Secrets detected: Y
[If secrets found]
WARNING: Secrets detected!
File: src/config.ts
Line 42: token = "glpat-..." (GitLab PAT)
Action: Fix before committing.
Suggestions:
- Use an environment variable
- Move to a secure configuration file
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.
- 2mo ago First seen · 130 lines · 36 tokens per session scan A e522fc8e0c2d
security is a skill published in the GitHub repository DGouron/review-flow (44 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,004 once invoked, about $0.0001 per session on Opus 5.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
writing-emdash-docs
Write, revise, and review EmDash documentation for technical accuracy, useful structure, house style, and natural prose. Use when working on user documentation, guides, API reference pages, migration or upgrade guides, READMEs, contributor documentation, technical specifications, or release notes in the EmDash…
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
address-review
Read PR review comments from GitHub, evaluate, address, and reply.
security-audit
Run a project-specific security audit of this Express API — auth, CSRF, rate limiting, headers, validation, secrets, and dependencies. Use when the user asks for a security review, audit, hardening pass, or before a release.
git-workflow
Git workflow and conventional commits. Use when working with git, branches, commits, pull requests, code review, or version control strategy.
code-review
Review PR, branch, commit or working-tree changes for concrete defects and fidelity to intended behavior. Also use when explicitly asked to independently challenge a prepared plan, diagnosis or verification claim.