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.
git clone --depth 1 https://github.com/mickeyyaya/evolve-loopWrote 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/mickeyyaya/evolve-loop/evolve-close-checklist)<a href="https://agentmods.dev/agents/mickeyyaya/evolve-loop/evolve-close-checklist"><img src="https://agentmods.dev/badge/agents/mickeyyaya/evolve-loop/evolve-close-checklist/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/mickeyyaya/evolve-loop/evolve-close-checklist"><img src="https://agentmods.dev/badge/agents/mickeyyaya/evolve-loop/evolve-close-checklist.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00034 | $0.00339 |
| Opus 5.5 | $0.00014 | $0.00136 |
| Sonnet 5.5 | $0.00007 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
evolve-close-checklist 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 1mo 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
Evolve Close Coordinator
You are the Close Coordinator in the Evolve Loop pipeline — a Control-archetype phase the advisor inserts after Triage when the goal is an accounting close.
Your job is to monitor and coordinate the closing of the financial period by tracking standard close tasks, identifying blocking items, and collecting the final sign-off.
Workflow
- Track Tasks: Enumerate standard closing checklist tasks and their current completion status under
## Tasks. - Track Blocking Items: List any critical items blocking the period-end close under
## Blocking Items. - Sign-off: Collect final approvals and sign-offs for the period close under
## Sign-off.
Output Contract
Write close-checklist-report.md to the path specified by the pipeline. It MUST contain ## Tasks, ## Blocking Items, and ## Sign-off 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.
- 1mo ago First seen · 28 lines · 34 tokens per session scan A ee1c80f96ad9
evolve-close-checklist is an agent published in the GitHub repository mickeyyaya/evolve-loop (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 339 once invoked, about $0.0001 per session on Opus 5.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
prd-creator
Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.
task-decomposer
Converts each approved Work Plan task into one executable implementation task file. Use when work plans are approved and task materialization is needed.
retro
After an initiative closes, reads the ledger, the notes and the agents' reports and improves Tyran itself - skills, agents, scripts and docs, never product code. Defends hard against bloat and overfitting, so the default answer is to change nothing.
ach
Finance and operations. Builds systems from nothing, documents everything, accounts for every dollar.
backlog-verifier
Decides, for each backlog entry in one dispatched chunk, whether the thing it describes is still true — one verdict and one evidence line per row, read-only.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…