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/bradygaster/squad/security-reviewnpx skills add bradygaster/squad --skill security-reviewgit clone --depth 1 https://github.com/bradygaster/squadWrote 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/bradygaster/squad/security-review)<a href="https://agentmods.dev/skills/bradygaster/squad/security-review"><img src="https://agentmods.dev/badge/skills/bradygaster/squad/security-review.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.00024 | $0.02669 |
| Opus 5 | $0.00012 | $0.01334 |
| Sonnet 5 | $0.00005 | $0.00534 |
| Haiku 4.5 | $0.00002 | $0.00267 |
Grade B, and why
security-review scanned grade B with 4 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 4d 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.
Unrestricted tool accesslowExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
A message containing "; rm -rf /" would execute arbitrary commands. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
A message containing "; rm -rf /" would execute arbitrary commands. Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
fetch(url, { headers: { Authorization: `Bearer ${apiKey}` } }); Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Child process execution (`child_process.exec`, `child_process.spawn`) How it starts
The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
Every PR that touches authentication, credentials, environment variables, file system operations, child process execution, user input handling, GitHub API calls, or workflow files must be reviewed for security. This skill provides a systematic checklist for catching security issues before they reach production.
Use this skill when a PR includes any of:
- Changes to
.github/workflows/files - New or modified environment variable usage
- File system read/write operations driven by user input
- Child process execution (
child_process.exec,child_process.spawn) - GitHub API calls (Octokit,
ghCLI wrappers) - New npm dependencies
- Credential or token handling
- Template rendering with dynamic values
Patterns
1. Secrets and Credentials
No secrets in source code — ever.
Review checklist:
- ❌ No API keys, tokens, passwords, or connection strings in committed files
- ❌ No hardcoded
GITHUB_TOKEN,NPM_TOKEN, or similar values - ❌ No
.envfiles committed (verify.gitignorecovers them) - ✅ Secrets must be referenced via
process.env.Xor${{ secrets.X }}in workflows - ✅ If the PR adds a new secret reference, verify it's documented in setup instructions
Watch for disguised secrets:
- Base64-encoded strings that decode to tokens
- URLs with embedded credentials (
https://user:token@host) - Test fixtures that contain real credentials from copy-paste
2. Personal Data in Committed Files
Personal data (especially email addresses) must never be written to committed files.
Squad-specific rule: git config user.email is explicitly banned from being written to any file that gets committed. This prevents PII leakage into the repository.
Review checklist:
- ❌ No email addresses written to committed files (even in config generation)
- ❌ No
git config user.emailoutput captured and stored in source - ✅ If user identity is needed at runtime, read it dynamically and never persist to a committed file
3. Environment Variable Safety
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.
- 4d ago First seen · 267 lines · 24 tokens per session scan B 1bc789a46d65
security-review is a skill published in the GitHub repository bradygaster/squad (3,154 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 2,669 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 4 findings (unrestricted tool access, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
coding-agents-farm
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
clean-architecture-dotnet
Use when domain logic leaks into API/Infrastructure, project references violate layer boundaries, or you need to decide between CQS (always), CQRS bus (complex domains), and DDD patterns (invariants and events).
mutation-testing
Use when running mutation testing, killing mutants, verifying test quality, checking mutation score, or analyzing survivors after the test baseline is green.
generate-microcks-openapi-samples
Use when creating OpenAPI mock examples for Microcks, setting up request/response routing with dispatchers, or mapping request fields to mock responses.
extracting-code-structure
Use when listing all methods, functions, or classes in a file, exploring unfamiliar code, getting API overviews, or deciding what to read selectively without loading entire files.
creating-dotnet-mcp-servers
Use when building Model Context Protocol (MCP) servers in .NET, configuring tools, transports (SSE/stdio), JSON serialization for AOT, or testing MCP endpoints.