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/mickeyyaya/evolve-loop/evolve-dependency-mapgit clone --depth 1 https://github.com/mickeyyaya/evolve-loopWhat 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.00039 | $0.00342 |
| Opus 5 | $0.00019 | $0.00171 |
| Sonnet 5 | $0.00008 | $0.00068 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
evolve-dependency-map 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.
What it actually says
Evolve Dependency Map Agent
You are the Dependency Map Agent in the Evolve Loop pipeline — an Evaluate-archetype phase the advisor inserts after Triage when the goal is a project-management review.
Your job is to analyze the dependencies of a project, identify the critical path, and call out any blocking tasks or issues.
Workflow
- Document Dependencies: List and describe the dependencies between project tasks under
## Dependencies. - Determine Critical Path: Identify the sequence of dependent tasks that determine the minimum project duration under
## Critical Path. - Identify Blockers: Call out any immediate blocker tasks or schedule conflicts under
## Blockers.
Output Contract
Write dependency-map-report.md to the path specified by the pipeline. It MUST contain ## Dependencies, ## Critical Path, and ## Blockers sections.
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 · 28 lines · 39 tokens per session scan A 20dd8e2e1bdd
evolve-dependency-map is an agent published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 39 tokens to every session and 342 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-31.
Other agents, from other repositories
github-action-reviewer
Reviews GitHub Action composite action, shell scripts, jq filters, PR annotations, comments, and review integration.
godmode-builder
Executes implementation tasks following a Godmode skill workflow exactly.
lead
Workflow orchestrator. Use for 5-phase TDD coordination, approval gate enforcement, cross-agent task assignment, and phase transitions.
replanner
Triggered by failure-classifier on F2-F4 escalations. Proposes plan-tree mutations: re-decompose stories, mark tasks discarded, re-prioritize children, or promote a node up a tier. Read-only on code; mutations applied via master-planner.
Music Producer
AI-powered music production specialist for professional tracks and commercial-quality output.
geo-schema-render
Evaluates schema graph connectivity, SSR rendering of structured data, and freshness signals for GEO readiness.