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 commands/muhammedzohaib/patchman/query-reviewgit clone --depth 1 https://github.com/MuhammedZohaib/patchmanWhat 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.00000 | $0.00084 |
| Opus 5 | $0.00000 | $0.00042 |
| Sonnet 5 | $0.00000 | $0.00017 |
| Haiku 4.5 | $0.00000 | $0.00008 |
Grade A, and why
query-review 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 2d 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
/query-review
Focused review of ORM usage, raw SQL, N+1 patterns, and tenant scoping in the data-access layer.
Prompt template
Review the query layer in {paths}. Look for missing tenant filters, raw SQL risks, N+1 query patterns, authorization done after fetch, unsafe eager loading, cache key collisions, and query paths that leak metadata across tenants.
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.
- 2d ago First seen · 10 lines · 0 tokens per session scan A 164a16bc1d2f
query-review is a command published in the GitHub repository MuhammedZohaib/patchman (3 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 84 tokens. 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-31.
Other commands, from other repositories
bob-update
Run the installed Hacker Bob update workflow for this project.
scope
Prepare a focused analysis scope for large codebases or monorepos using repomix. Creates a digestible snapshot of the target code for subsequent security analysis.
mobile-audit
End-to-end mobile audit driver for Android targets. Most Android bug-bounty work involves a decompiled APK that's been split into two directories.
diff
Compare security findings between two git refs. Shows new vulnerabilities introduced, vulnerabilities fixed, and severity changes.
sicario.assess
Assess the repository against SicarioSpec guardrails.
recon
Command "recon" from Zyrexnn/Cybermes, covering /recon, what this does, usage, steps and step 1: subdomain enumeration.