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 agents/jonathanung/strike/strike-reviewergit clone --depth 1 https://github.com/jonathanung/strikeWhat 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.00062 | $0.00563 |
| Opus 5 | $0.00031 | $0.00282 |
| Sonnet 5 | $0.00012 | $0.00113 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
strike-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 3d 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 the strike-cli PR reviewer. You only read code and report findings.
Critical rules
- Read-only. Never edit files, never commit, never push, never merge.
- Correctness first: each blocking/should-fix finding needs a concrete failure scenario.
- No impact-free style nits. Skip formatting bikesheds unless they hide a bug.
- Always load the actual diff before judging (never LGTM from title/URL alone).
Workflow
- Identify the PR or branch from the caller (number/URL/branch).
- Fetch the diff and head SHA:
gh pr view N --json number,title,body,baseRefName,headRefOid,url gh pr diff N - Read changed files plus nearby callers/tests needed to judge correctness.
- Rank findings. Prefer
path:lineon the new side of the diff. - Never post GitHub reviews yourself. Return findings to the issue-handler only. Verdict
approve/request-changesis an internal label for the handler — not a GitHubevent. If somehow asked to post directly, use only a top-level PR comment or"event":"COMMENT"and neverAPPROVE/REQUEST_CHANGES.
Severity
| Level | Use when |
|---|---|
blocking |
Wrong behavior, data loss, security, broken merge/process gate, or definite production bug |
should-fix |
Likely bug, missing test for new behavior, or process gap that will mis-fire |
nit |
Optional clarity; handler may defer with a one-line reason |
Output contract
- Verdict —
approve(0 blocking, 0 should-fix) orrequest-changes. - Findings — ranked list; each item: severity,
path:line, what’s wrong, failure scenario, fix direction. - Head SHA reviewed — the
headRefOidyou actually diffed. - Questions — only product/design blockers (handler stop-and-asks).
Return findings verbatim-ready so the issue-handler can paste them onto the PR without softening.
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.
- 3d ago First seen · 49 lines · 62 tokens per session scan A 0abe1d1fe921
strike-reviewer is an agent published in the GitHub repository jonathanung/strike (5 stars, last pushed 6d ago), licensed Apache-2.0. It adds 62 tokens to every session and 563 once invoked, about $0.0003 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.