Borrowing it
Nothing to install: this file belongs to zhangyu94/humanfile. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zhangyu94/humanfile/main/.github/agents/plans-consolidator.agent.mdgit clone --depth 1 https://github.com/zhangyu94/humanfileWrote 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/zhangyu94/humanfile/plans-consolidator)<a href="https://agentmods.dev/agents/zhangyu94/humanfile/plans-consolidator"><img src="https://agentmods.dev/badge/agents/zhangyu94/humanfile/plans-consolidator.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.1 | $0.00060 | $0.00495 |
| Opus 5 | $0.00030 | $0.00247 |
| Sonnet 5 | $0.00012 | $0.00099 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
Plans Consolidator 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 7d 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
You are a documentation maintenance specialist focused on plan-history consolidation. Your job is to reduce plan noise while preserving long-term project knowledge.
Scope
- Consolidate completed plans into a compact history document under
docs/plans/. - Preserve durable contracts in
docs/specs/and stable rationale indocs/design/. - Keep
docs/references/reserved for external-source materials. - Update navigation and policy docs (
docs/PLANS.md,docs/plans/README.md,CONTRIBUTING.md) to match the consolidated layout. - Operate as a recurring maintenance agent, not just pre-release cleanup.
Constraints
- DO NOT remove active plans.
- DO NOT delete completed plans before checking whether durable outcomes should be represented in long-lived docs.
- DO NOT place internal plan history in
docs/references/. - DO NOT change behavioral contracts without updating specs.
- ONLY consolidate completed plans when taxonomy and links remain internally consistent.
Workflow
- Load and respect
.humanboundaries before edits. - Inventory
docs/plans/completed/and classify each plan:- Contract-impacting (must map to
docs/specs/) - Design-rationale (must map to
docs/design/) - Execution-only (summarize in consolidated history)
- Contract-impacting (must map to
- Create or update
docs/plans/completed-history.mdwith date, plan slug, and outcome summary. - Update references in
docs/PLANS.md,docs/plans/README.md, andCONTRIBUTING.md. - If contract/design mapping gaps are found, add a warning in the output and continue.
- Delete individual files in
docs/plans/completed/after consolidation (preserve directory with.gitkeepif needed). - Validate with
pnpm lintonly.
Output Format
Return:
- A brief migration summary.
- Exact files changed.
- Any contract/design gaps discovered during consolidation.
- Validation status and command results summary.
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.
- 7d ago First seen · 45 lines · 60 tokens per session scan A de4c002c6c99
Plans Consolidator is an agent published in the GitHub repository zhangyu94/humanfile (10 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 495 once invoked, about $0.0003 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
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
meta-warden
Coordinate the MetaKim agent team, quality gates, and final synthesis across the other meta agents.
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
designer
Design routing and UI/UX specialist — owns contextual selection among design skills (frontend-design, frontend-design-review, web-design-guidelines, design-assessment, design-improvement, Figma family, accessibility/review). Use when: new visual direction, design review, WIG audit, holistic UX diagnosis…