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/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/gh-security-review)<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/gh-security-review"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/gh-security-review/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/commands/synaptiai/synapti-marketplace/gh-security-review"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/gh-security-review.svg" alt="Reviewed on agentmods" width="80" 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.00013 | $0.03184 |
| Opus 5 | $0.00006 | $0.01592 |
| Sonnet 5 | $0.00003 | $0.00637 |
| Haiku 4.5 | $0.00001 | $0.00318 |
Grade A, and why
gh-security-review scanned grade A with 1 finding 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 yesterday.
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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
'(exec|spawn|system|popen|subprocess|child_process|os\.system|eval\()' 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Review
Dedicated security review of current branch changes. Scans for secrets, injection vectors, auth gaps, data exposure, and dependency vulnerabilities.
Tool Usage: This workflow uses the AskUserQuestion tool for severity confirmation and remediation decisions, and TaskCreate/TaskUpdate for tracking findings.
Contract
GOAL: Identify all security-relevant issues in current diff with actionable findings. Testable: every finding has a CWE reference and file:line location.
CONSTRAINTS:
- Must check for hardcoded secrets in every review
- Must analyze injection vectors for any user-input handling code
- All findings must include file:line references
- Never auto-fix security issues without user approval
FORMAT: P1/P2/P3 findings table with CWE references, file:line locations, and suggested fixes.
FAILURE CONDITIONS (output is unacceptable if any apply):
- Completed without checking for hardcoded secrets
- Injection vectors not analyzed for code handling user input
- Findings lack file:line references
- CWE references missing from findings
- Security issues auto-fixed without user approval
- Review completed without scanning dependency vulnerabilities (when package manager exists)
Phase 1: Scope Detection
Execute in parallel:
-
Get the diff to review:
DEFAULT_BRANCH=$(gh repo view --json defaultBranchRef --jq '.defaultBranchRef.name') git diff origin/$DEFAULT_BRANCH..HEAD --name-only -
Get full diff content:
git diff origin/$DEFAULT_BRANCH..HEAD -
Detect tech stack for targeted scans:
ls pyproject.toml package.json go.mod Cargo.toml Gemfile 2>/dev/null -
Check for security-relevant config files:
ls .env* *.pem *.key *.cert docker-compose*.yml Dockerfile 2>/dev/null
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.
- yesterday First seen · 371 lines · 13 tokens per session scan A 80dbd5cc754a
gh-security-review is a command published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 3,184 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-10.
Other commands, from other repositories
cc-review
(Conductor) Review code changes against spec and standards.
create-worktree
Follow these steps to create a git worktree.
production-upgrade
Run the full product upgrade pipeline — 55-agent iterative review with CEO/Engineering/UX/QA parallel loops.
review
Pre-landing code review — analyzes diff for SQL safety, LLM trust boundaries, conditional side effects, missing tests, dependency risks, and security issues.
review
Run code-review and security-review skills against the current diff. Safe to run repeatedly during Build.
checklist
Generate a custom checklist for the current feature based on user requirements.