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/sergeyklay/.agentsWrote 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/sergeyklay/.agents/challenge-pr.body)<a href="https://agentmods.dev/commands/sergeyklay/.agents/challenge-pr.body"><img src="https://agentmods.dev/badge/commands/sergeyklay/.agents/challenge-pr.body/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/sergeyklay/.agents/challenge-pr.body"><img src="https://agentmods.dev/badge/commands/sergeyklay/.agents/challenge-pr.body.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.00000 | $0.00005 |
| Opus 5 | $0.00000 | $0.00003 |
| Sonnet 5 | $0.00000 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00001 |
Grade A, and why
challenge-pr.body 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 10d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- resolve-review.body — 100% identical, 0 lines differ
- make-pr.body — 100% identical, 0 lines differ
What it actually says
$ARGUMENTS
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.
- 10d ago First seen · 2 lines · 0 tokens per session scan A 3e6da874d3ca
challenge-pr.body is a command published in the GitHub repository sergeyklay/.agents (5 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 5 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
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
ship
Seen on their staging, then live. Rollback you have run.
speckit.polish
Polish and complete speckit workflow — quality gate, docs, changelog, MR.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
review
Recent git commits: !git log --oneline -10.
visualize
Open the local PI decision visualizer. Start the visualizer server backed by /.pi/decisions data, and open the result in the browser unless --no-open is passed.