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/sergeyklay/.agents/implementgit clone --depth 1 https://github.com/sergeyklay/.agentsWhat 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.00021 | $0.00147 |
| Opus 5 | $0.00010 | $0.00073 |
| Sonnet 5 | $0.00004 | $0.00029 |
| Haiku 4.5 | $0.00002 | $0.00015 |
Grade A, and why
implement 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
Your task is to run the complete implementation pipeline for the request below.
The pipeline:
- Assesses the input - determines the route (plan-driven, issue-driven, or description-driven) and whether a specification is needed first
- Implements - delegates to the implementation agent with full architectural context
- Checks for spec deviations - inspects
.findings/for issues discovered during implementation - Tests - delegates to the tester agent with the implementation summary
Follow your protocol strictly. Do not skip any phase. Track progress with the todo list.
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 · 15 lines · 21 tokens per session scan A 55e015a31a45
implement is a command published in the GitHub repository sergeyklay/.agents (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 21 tokens to every session and 147 once invoked, about $0.0001 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 commands, from other repositories
template
Manage issue templates for streamlined issue creation.
cross-validate
Take a specific scientific claim and confirm or refute it across 3+ independent databases, then report concordance. Use before publishing, citing, or acting on a fact when you want to know how strongly it's supported. Forces multi-source verification that the agent doesn't naturally enforce.
translate-id
Resolve an identifier across all relevant namespaces (HGNC symbol, Ensembl, UniProt, NCBI Gene ID, RefSeq, MGI, OMIM, ChEMBL, PubChem, etc.). Detects the input namespace automatically, picks the right resolver tool, and returns a complete cross-reference table. Use when you have an ID in one namespace and need it in…
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
discover
Search the Everruns(Dev) API catalog for available operations.
fix
Universal debugging and fix application with semantic code analysis.