Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ilyasibrahim/claude-agents-coordinationnpx agentmods add commands/ilyasibrahim/claude-agents-coordination/archiveWrote 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/ilyasibrahim/claude-agents-coordination/archive)<a href="https://agentmods.dev/commands/ilyasibrahim/claude-agents-coordination/archive"><img src="https://agentmods.dev/badge/commands/ilyasibrahim/claude-agents-coordination/archive.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.00017 | $0.00676 |
| Opus 5 | $0.00009 | $0.00338 |
| Sonnet 5 | $0.00003 | $0.00135 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
archive 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.
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.
Archive Registry
Move registry entries and reports older than N days to archive.
REPORTS_DIR=".claude/reports" ARCHIVE_DIR="$REPORTS_DIR/archive" REGISTRY="$REPORTS_DIR/_registry.md"
Process
- Parse active registry for entries older than threshold (default: 7 days)
- Move report files to
.claude/reports/archive/[category]/ - Create dated archive registry
.claude/reports/archive/_registry-archive-YYYYMMDD.md - Update active registry (remove archived entries)
- Set status of archived entries to "Archived" in dated registry
- Report summary with archive date and file count
Arguments
$ARGUMENTS: Days threshold (default: 7)/archive- Archive entries older than 7 days/archive 14- Archive entries older than 14 days/archive 3- Archive entries older than 3 days
Archive Structure
.claude/reports/archive/
├── _registry-archive-YYYYMMDD.md # Dated archive registries (snapshots)
├── README.md # Archive index and documentation
├── analysis/ # Old analysis reports
├── arch/ # Old architecture reports
├── bugs/ # Old bug reports
├── design/ # Old design reports
├── implementation/ # Old implementation reports
├── exec/ # Old execution reports
├── handoff/ # Old handoff reports
├── review/ # Old review reports
├── security/ # Old security reports
└── tests/ # Old test reports
Execution
Uses the Python archive script bundled with the agent-coordination skill:
# Script location (per Claude Code skill structure)
python .claude/skills/agent-coordination/scripts/archive_reports.py [days]
# Examples
python .claude/skills/agent-coordination/scripts/archive_reports.py # Default: 7 days
python .claude/skills/agent-coordination/scripts/archive_reports.py 14 # 14 days
python .claude/skills/agent-coordination/scripts/archive_reports.py 7 --dry-run # Preview only
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 · 78 lines · 17 tokens per session scan A e66190eb0bae
archive is a command published in the GitHub repository ilyasibrahim/claude-agents-coordination (83 stars, last pushed 3mo ago), licensed Unlicense. It adds 17 tokens to every session and 676 once invoked, about $0.0001 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.