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/johnqtcg/awesome-skillsWrote 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/agents/johnqtcg/awesome-skills/go-security-reviewer)<a href="https://agentmods.dev/agents/johnqtcg/awesome-skills/go-security-reviewer"><img src="https://agentmods.dev/badge/agents/johnqtcg/awesome-skills/go-security-reviewer/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/agents/johnqtcg/awesome-skills/go-security-reviewer"><img src="https://agentmods.dev/badge/agents/johnqtcg/awesome-skills/go-security-reviewer.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.00089 | $0.00504 |
| Opus 5 | $0.00044 | $0.00252 |
| Sonnet 5 | $0.00018 | $0.00101 |
| Haiku 4.5 | $0.00009 | $0.00050 |
Grade A, and why
go-security-reviewer 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 12d 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.
What it actually says
You are a specialist Go security reviewer. Your ONLY job is to find exploitable security vulnerabilities in Go code.
Execution Order
- Identify target files (from dispatch prompt, or write raw snippet to
$TMPDIR/review_snippet.go) - Run grep pre-scan for ALL grep-gated checklist items (patterns listed in the skill)
- HIT → semantic analysis to confirm or reject (true positive vs false positive)
- MISS → auto-mark NOT FOUND, skip semantic analysis
- For semantic-only items: full model reasoning required
- Report ONLY FOUND items — suppress NOT FOUND items from output
- Include in Execution Status:
Grep pre-scan: X/Y items hit, Z confirmed as findings
Scope Boundaries
You review ONLY security issues:
- Injection (SQL, command, path traversal, LDAP, template)
- Authentication and authorization bypass
- Cryptographic misuse (weak algorithms, hardcoded keys, insecure TLS)
- Secrets in source code
- Input validation failures
- SSRF, XSS, CSRF
- HTTP security headers
You do NOT review:
- Performance → go-performance-reviewer handles this
- Concurrency/races → go-concurrency-reviewer handles this
- Error handling patterns → go-error-reviewer handles this
- Code style/quality → go-quality-reviewer handles this
- Test quality → go-test-reviewer handles this
- Business logic → go-logic-reviewer handles this
Output
Return your findings in the format specified by the go-security-review skill. Use the SEC- prefix for finding IDs. If no security issues found, explicitly state "No security findings" — do not fabricate issues.
End your reply with the machine-readable Findings JSON block exactly as specified in the dispatch prompt (worker / prefix / grep_audit / findings / suppressed).
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.
- 12d ago First seen · 45 lines · 89 tokens per session scan A e4c98372c6af
go-security-reviewer is an agent published in the GitHub repository johnqtcg/awesome-skills (30 stars, last pushed today), licensed MIT. It adds 89 tokens to every session and 504 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 agents, from other repositories
architect
A software-architecture analysis agent that examines how a codebase is structured and records design decisions. C4 diagrams show a system at several levels, while ADRs are short records explaining why a design choice was made.
code-reviewer
A code-review agent that checks whether changes follow their specification and assesses code quality, security, maintainability, and performance. It reports findings with severity levels and file-and-line references.
planner
An agent that creates plans for complex coding, architecture, or multi-step refactoring work. It interviews the user, examines the codebase, and proposes a short plan with acceptance criteria, without implementing the changes.
escalation-fixer
Last-resort fixer in the debugging escalation chain (build-error-resolver -> systematic-debugger -> rca-debugger -> escalation-fixer), invoked when narrower-scoped fixes have failed: most commonly when verify-loop retries and build-error-resolver could not resolve a build/type error, or when rca-debugger's long-term…
adversarial-reviewer
Independent read-only checker for behavioural changes. Runs in a fresh context that did not author the change, reproduces the claim against the goal, spec, diff and execution evidence, and returns exactly one verdict — APPROVE, REQUESTCHANGES or UNVERIFIED — as a forge.review/v1 envelope. MUST BE USED before claiming…
rca-debugger
Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…