Borrowing it
Nothing to install: this file belongs to hackerpug-ai/holocron. 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/hackerpug-ai/holocron/main/.claude/commands/close-improvements.mdgit clone --depth 1 https://github.com/hackerpug-ai/holocronWrote 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/commands/hackerpug-ai/holocron/close-improvements)<a href="https://agentmods.dev/commands/hackerpug-ai/holocron/close-improvements"><img src="https://agentmods.dev/badge/commands/hackerpug-ai/holocron/close-improvements/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/commands/hackerpug-ai/holocron/close-improvements"><img src="https://agentmods.dev/badge/commands/hackerpug-ai/holocron/close-improvements.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.00015 | $0.00824 |
| Opus 5.5 | $0.00006 | $0.00330 |
| Sonnet 5.5 | $0.00003 | $0.00165 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
close-improvements 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 13d 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/close-improvements
Audit every open improvement request in the holocron MCP against the current codebase, then auto-close the ones that evidence shows are already implemented. No approval gate — open items that have been shipped get closed; partial/not-done stay open.
Workflow
1. List open improvements
Call mcp__holocron__listImprovementsTool with { status: "open", limit: 100 }. For each returned item, capture:
_idtitleanddescription(truncate description to ~200 chars for the audit prompt)sourceScreen/sourceComponent(hints about where in the app this lives)
If the list is large (>6 items), process in parallel batches — one Explore agent per improvement, dispatched in a single message.
2. Dispatch parallel Explore agents
For each open improvement, dispatch an Explore subagent with a tight, evidence-based prompt:
I need to determine whether this improvement request has been implemented in the holocron codebase.
Improvement: {title}
Description: {description}
Source: {sourceScreen}/{sourceComponent}
Search the codebase for relevant files and return ONE of these verdicts with evidence:
- IMPLEMENTED — the improvement is fully shipped. Cite 1-3 specific file paths (with line numbers if helpful) that prove it. Be strict: partial implementations are NOT implemented.
- PARTIAL — some of it is done but key pieces are missing. Cite what's done and what's missing.
- NOT_DONE — no trace in the codebase, or the improvement describes something that clearly doesn't exist yet.
Keep your response under 100 words. Format:
VERDICT: {IMPLEMENTED|PARTIAL|NOT_DONE}
EVIDENCE:
- {file path 1}: {why this proves it}
- {file path 2}: {why this proves it}
3. Close IMPLEMENTED items
For each agent verdict of IMPLEMENTED, call mcp__holocron__closeImprovementTool (or setImprovementStatusTool with status=closed) with:
id: the improvement_idreason:"Auto-closed by codebase audit on {YYYY-MM-DD}: {1-sentence why}"evidence: array of file paths from the agent's EVIDENCE section
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.
- 13d ago First seen · 78 lines · 15 tokens per session scan A 74aff4ac0b1b
close-improvements is a command published in the GitHub repository hackerpug-ai/holocron (0 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 824 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-10-02.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.