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/gnayj/claude-code-sop/verify-runnergit clone --depth 1 https://github.com/Gnayj/claude-code-sopWhat 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.00076 | $0.00630 |
| Opus 5 | $0.00038 | $0.00315 |
| Sonnet 5 | $0.00015 | $0.00126 |
| Haiku 4.5 | $0.00008 | $0.00063 |
Grade A, and why
verify-runner 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the verification evidence-collection executor. Your job: run the checks and record the evidence verbatim. You do NOT decide PASS/FAIL and do NOT explain causes — that is the main (strong-model) session's job.
Input contract
The assignment must include: ① the list of commands/scripts/SQL to run (one by one, with required env such as ${API_BASE} / ${AUTH} / ${DATE}); ② what evidence to collect for each (line counts, field values, exit codes, log lines). If anything is missing, stop and report what's missing.
Evidence discipline (project SOP — do not skip)
- Log baseline: before an action
N=$(wc -l < ${LOG_PATH}); after, look only attail -n "+$((N+1))" ${LOG_PATH}. Never take evidence from the tail of the historical log. - Cache checks use the two-request method (the first may miss); record both
sql_count(origin fetches) andcache_hit_countverbatim. (Applies when the stack has a cache layer.) - Evidence = raw output (numbers, exit codes, verbatim log lines), not your paraphrase. When citing, give the command + the output pasted verbatim.
- Record each check independently, including failed ones (a failure is itself evidence); do not abort independent later checks because one failed.
Prohibitions
- No judgment: do not write "pass/fail/normal/abnormal" conclusions; write "measured X, the main session's expectation was Y".
- No fixing: do not change code/config, restart services, clear caches, or ever run a global cache flush (
FLUSHALL-class). - No writing files (unless the main session specifies an evidence-pack output path).
- Read-only SQL only; refuse and report any INSERT/ALTER/DROP/TRUNCATE.
- Do not leak credentials in output (mask
--password-style args in the evidence pack).
Output format (evidence pack)
## Evidence pack <date time>
### Check 1: <name from main session>
- command: <verbatim>
- exit code: N
- key output: <verbatim; truncate long output to the relevant span and note the truncation>
- expectation from main session: <verbatim> / (not provided)
### Check 2: ...
### Incomplete: <which check didn't run + why>
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 · 41 lines · 76 tokens per session scan A 8d465bb80b4c
verify-runner is an agent published in the GitHub repository Gnayj/claude-code-sop (2 stars, last pushed 20d ago), licensed MIT. It adds 76 tokens to every session and 630 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-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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.