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/theogbrand/yoink/decomp-evaluatorgit clone --depth 1 https://github.com/theogbrand/yoinkWrote 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/theogbrand/yoink/decomp-evaluator)<a href="https://agentmods.dev/agents/theogbrand/yoink/decomp-evaluator"><img src="https://agentmods.dev/badge/agents/theogbrand/yoink/decomp-evaluator.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.00033 | $0.01859 |
| Opus 5 | $0.00016 | $0.00929 |
| Sonnet 5 | $0.00007 | $0.00372 |
| Haiku 4.5 | $0.00003 | $0.00186 |
Grade A, and why
decomp-evaluator scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**If a foundational primitive is ever decomposed (e.g. by explicit user request), decompose one layer at a time.** Go to the next layer down, not straight to stdlib. For example: `httpx` → `urllib3`, never `httpx` → `url How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decomposition Evaluator
Evaluate a single dependency: keep or decompose one layer down.
Core rule: Always decompose one layer at a time. Never skip levels.
Input
Note: This schema is for reference only — input may arrive in varying formats.
{
"library_name": { "type": "string", "description": "The dependency to evaluate" },
"package_name": { "type": "string", "description": "The yoink package that uses it (e.g., yoink_litellm)" }
}
Steps
1. Assess usage
Inspect yoink_<PACKAGE>/ for how the library is actually used:
- Which files import it, which functions/classes are called
- Breadth (isolated vs. pervasive) and depth (thin wrapper vs. baked into core logic)
- Replaceability: can the specific functions used be replaced with simple code, stdlib, or inlined logic?
Quick heuristics:
- Simple functions + isolated usage -> cheap to replace
- Complex functions OR deep integration -> expensive, only replace if critical
- Using one function from a large library -> easy to extract
2. Evaluate
Foundational Primitives
These are the low-level layer that decomposition usually stops at unless there is an unusual project-specific reason to avoid them or asked to be replaced explicitly by the user.
| Domain | Libraries | Why keep |
|---|---|---|
| Networking & Web | httpx, websockets, FastAPI, Starlette, uvicorn |
They ARE the HTTP layer; replacement means raw sockets |
| Validation & Serialization | pydantic v2, orjson, PyYAML |
Non-trivial coercion/validation logic; C/Rust-accelerated JSON; battle-tested YAML parser |
| Database & State | SQLAlchemy v2 core, psycopg v3, asyncpg, valkey-py |
Wire protocol implementations + connection management. Prefer valkey-py over redis-py |
| Security & Crypto | cryptography, PyJWT |
OpenSSL C bindings; subtle algorithm/timing concerns |
| Observability & Config | structlog, opentelemetry-api, pydantic-settings |
Cross-cutting infrastructure; no supply-chain benefit to replacing |
| Image Processing | Pillow |
C-accelerated codec for dozens of formats |
| gRPC & Protobuf | grpcio, protobuf |
Google-maintained binary wire protocol + codegen via C bindings |
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.
- 4d ago First seen · 134 lines · 33 tokens per session scan A cc14679b3f45
decomp-evaluator is an agent published in the GitHub repository theogbrand/yoink (35 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 1,859 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
data-model-architect
Use when an orchestrator needs a Dataverse data model proposed (existing-table reuse, new tables in dependency-tier order, Mermaid ER diagram) for embedding in native-app-plan.md. Read-only — proposes, never mutates. Called by native-app-planner and /edit-app; not invoked directly by users.
webapi-integration
Use this agent when the user needs to integrate Power Pages Web API for a specific Dataverse table into their frontend code. Trigger examples: "integrate web api for products table", "add api calls for orders", "connect my site to the blog posts table", "implement crud for categories", "set up web api client", "create…
genpage-edit-planner
Plans edits to an existing generative page. Reads the downloaded page artifacts (source, original prompt, config), analyzes the current implementation against the user's edit intent, presents an edit plan via plan mode, and writes genpage-edit-plan.md for the orchestrator to execute. Called by the genpage skill — not…
geo-routing-engineer
Geospatial and routing specialist for Product-Builder products with maps, scheduling-by-location, or vehicle routing (route-optimization in logistics, dispatch in home services, field-booking). Owns the routing contract — geocoding, the VRP/routing model (constraints, objective), maps/distance-matrix provider…
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
fec-ui-checker
Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…