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/davdittrich/delegate-agy/agy-delegate-searchgit clone --depth 1 https://github.com/davdittrich/delegate-agyWrote 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/agents/davdittrich/delegate-agy/agy-delegate-search)<a href="https://agentmods.dev/agents/davdittrich/delegate-agy/agy-delegate-search"><img src="https://agentmods.dev/badge/agents/davdittrich/delegate-agy/agy-delegate-search.svg" alt="Measured on agentmods" 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 | $0.00048 | $0.00572 |
| Opus 5 | $0.00024 | $0.00286 |
| Sonnet 5 | $0.00010 | $0.00114 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
agy-delegate-search 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 58 lines · 48 tokens per session scan A c0a2a5c0e2f0
agy-delegate-search is an agent published in the GitHub repository davdittrich/delegate-agy (15 stars, last pushed 10d ago), with no licence file. It adds 48 tokens to every session and 572 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
gemini-rescue
Hand a task the user has asked to give to Gemini or AGY -- investigation, diagnosis, a second implementation pass, or a substantial coding task -- to the shared companion runtime. Use only when the user has asked for Gemini or AGY.
bulk-test-writer
Writes tests for existing behaviour. Adds and edits test files only — never touches production code. Use for coverage backfill where the bulk of the work is mechanical.
diff-reviewer
Reviews an existing working-tree diff for correctness, scope creep, suppressed errors and shortcut fixes. Reports findings only — never edits. Use as a second opinion before the driver accepts a worker's changes.
repo-inventory
Read-only surveyor. Maps a repository's architecture, entry points, dependencies, test commands and risky areas without modifying anything. Use before any implementation work so the driver can scope a task accurately.
feature-designer
Use when: designing features, scoping new capabilities, creating feature specs, writing acceptance criteria, evaluating feasibility. Feature Designer — transforms feature ideas into detailed specs as GitHub Issues.
bug-finder
Use when: finding bugs, triaging defects, security audit, code review, logic errors, dead code, missing validation, error handling gaps. Bug-Finder — systematic codebase analysis producing GitHub Issues.