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/yelmuratoff/agent_sync/code-reviewergit clone --depth 1 https://github.com/yelmuratoff/agent_syncWhat 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.00038 | $0.00351 |
| Opus 5 | $0.00019 | $0.00176 |
| Sonnet 5 | $0.00008 | $0.00070 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
code-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 yesterday.
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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- yesterday First seen · 31 lines · 38 tokens per session scan A 44988d0532f7
code-reviewer is an agent published in the GitHub repository yelmuratoff/agent_sync (14 stars, last pushed yesterday), licensed GPL-3.0. It adds 38 tokens to every session and 351 once invoked, about $0.0002 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-30.
Other agents, from other repositories
hyperresearch-depth-investigator
Use this agent in Layer 3 of the hyperresearch deep research pipeline. Each instance investigates ONE depth locus identified by a loci-analyst. The agent reads existing vault sources relevant to the locus, fetches new sources as needed (via the hyperresearch-fetcher subagent), and writes ONE interim report note…
hyperresearch-fetcher
Research fetcher with primary-source-chasing agency. Fetches assigned URLs, reads and summarizes content, extracts structured claims, then follows citation chains and references to discover and fetch primary sources the secondary sources cite. Needs solid comprehension and judgment. Spawn multiple in parallel for bulk…
Analytics Engineer
Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.
CocoWatch
Non-blocking developer engagement observer. Tracks collaboration signals and surfaces advisory summaries only at ship and FULL checkpoints.
Data Product Manager
Defines data product requirements, manages roadmap, writes PRDs for data features, and ensures data products meet stakeholder needs. Invoke with $dpm.
Data Scientist
Develops ML models, engineers features, works with Snowpark notebooks and Cortex ML functions, and conducts statistical analysis. Invoke with $ds.