What is evolve-close-checklist?

An agent that coordinates an accounting close, the process of completing and approving a financial period's records.

Use it to track standard close tasks, list items preventing completion, and collect sign-offs in a structured report.

It keeps unfinished tasks and blockers visible and makes sure the final approval is recorded.

evolve-close-checklist — Agent by mickeyyaya

Install

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.

agentmods

npx agentmods add agents/mickeyyaya/evolve-loop/evolve-close-checklist

Clone the repo

git clone --depth 1 https://github.com/mickeyyaya/evolve-loop

Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 339 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00034	$0.00339
Opus 5	$0.00017	$0.00169
Sonnet 5	$0.00007	$0.00068
Haiku 4.5	$0.00003	$0.00034

Measured 2d ago against content hash ee1c80f96ad9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

agents/evolve-close-checklist.md · 28 lines

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.

Changes

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.

2d ago First seen · 28 lines · 34 tokens per session scan A ee1c80f96ad9

Subscribe to this mod's changes

evolve-close-checklist is an agent published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 34 tokens to every session and 339 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.

Finance and fintech Project management ai-agents ai-pipeline autonomous-coding claude-code claude-code-plugin code-quality

finance-reviewer

Finance + FinOps specialist — pricing, billing, unit economics, cloud cost, capacity planning, ROI analysis, budget impact, financial reporting integrity. Use PROACTIVELY on pricing / billing / plan-tier changes, cost-sensitive cloud resources, instance sizing, autoscaling bounds, data transfer patterns…

Nmor/the-claude-council · 76 tokens

payments-reviewer

Payments + PCI-DSS + open-banking + escrow specialist. Use PROACTIVELY when code touches card / bank / wallet / instant-rail payments, refunds, chargebacks, subscriptions, payouts, escrow, trust-account segregation, or ledger reconciliation. Reviews 3DS2 + SCA, network tokenization, webhook signature verification…

Nmor/the-claude-council · 117 tokens

eval-curator

Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…

hyhmrright/brooks-lint · 97 tokens

evolve-close-checklist