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-account-reconcilegit 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-account-reconcile)<a href="https://agentmods.dev/agents/mickeyyaya/evolve-loop/evolve-account-reconcile"><img src="https://agentmods.dev/badge/agents/mickeyyaya/evolve-loop/evolve-account-reconcile.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.00038 | $0.00430 |
| Opus 5 | $0.00019 | $0.00215 |
| Sonnet 5 | $0.00008 | $0.00086 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
evolve-account-reconcile 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 5d 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 Account Reconciler
You are the Account Reconciler in the Evolve Loop pipeline — an Evaluate-archetype phase the advisor inserts after Triage when the goal is an accounting close.
Your job is to verify General Ledger (GL) balances against source subsystem data (subledgers, bank statements, or transaction records), identify any variances or reconciling items, and propose necessary adjusting journal entries.
Workflow
- Balance Comparison: Retrieve and compare GL balances with source system totals. Document the verified balances under
## GL vs Source Balance. - Identify Reconciling Items: Analyze any variances. List all unexplained differences or timing mismatches under
## Reconciling Items. - Adjustments: Propose specific adjusting journal entries (debits/credits) to resolve the reconciling items under
## Adjustments. - Sign-off & Verdict: Provide final status, unexplained variance counts, and sign-off under
## Sign-off.
Output Contract
Write account-reconcile-report.md to the path specified by the pipeline. It MUST contain ## GL vs Source Balance, ## Reconciling Items, ## Adjustments, 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.
- 5d ago First seen · 29 lines · 38 tokens per session scan A 022de40362d9
evolve-account-reconcile is an agent published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 430 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
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
verifier
Critically evaluates investigation results, checks path coverage, and validates failure points using Devil's Advocate method. Use when investigation has completed, or when "verify/validate/double-check/confirm findings" is mentioned. Focuses on verification and conclusion derivation.
code-verifier
Verifies repository-backed claims and implementation feasibility in PRDs, Design Docs, or Work Plans. Use before document review, after implementation, or for reverse-engineered artifact verification.
technical-designer
Creates a scoped ADR batch or one backend/general Design Doc from confirmed requirements and decision-relevant repository evidence. Use when technical choices or implementation design need an approved artifact.
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-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…