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.
git clone --depth 1 https://github.com/ofirbuchshtav-lgtm/claude-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/ofirbuchshtav-lgtm/claude-archive/caa-add-latest)<a href="https://agentmods.dev/commands/ofirbuchshtav-lgtm/claude-archive/caa-add-latest"><img src="https://agentmods.dev/badge/commands/ofirbuchshtav-lgtm/claude-archive/caa-add-latest/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/ofirbuchshtav-lgtm/claude-archive/caa-add-latest"><img src="https://agentmods.dev/badge/commands/ofirbuchshtav-lgtm/claude-archive/caa-add-latest.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.00023 | $0.00252 |
| Opus 5 | $0.00012 | $0.00126 |
| Sonnet 5 | $0.00005 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
CAA-add-latest 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 12d 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
The human just said "that was valuable — archive it." Take the MOST RECENT non-trivial fix/discovery from this session and file it into the Claude Archive with no further questions (only pause if consent is missing or the fix contains something private that needs their call).
Follow the exact procedure in /CAA-add (locate archive → quality gate → give → honest self-score → commit/sync → one-line report), with these overrides:
- Target selection is automatic: the latest thing that took real effort — a bug that resisted the first attempt, a non-obvious configuration, a version-specific breakage, an API surprise. If the latest fix is trivial or purely project-specific, archive nothing and say why in one sentence.
- Bias to speed: draft tight, score honestly, ship. The whole operation should feel like a reflex, not a ceremony.
- Remember the exact-error rule: the error text goes in
## Problemverbatim — that string is the next Claude's search query and the whole reason this archive wins.
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.
- 12d ago First seen · 13 lines · 23 tokens per session scan A 179752c7acfc
CAA-add-latest is a command published in the GitHub repository ofirbuchshtav-lgtm/claude-archive (0 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 252 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-31.
Other commands, from other repositories
context-save
An elite context engineering specialist focused on comprehensive, semantic, and dynamically adaptable context preservation across AI workflows. This tool orchestrates advanced context capture, serialization, and retrieval strategies to maintain institutional knowledge and enable seamless multi-session collaboration.
wiki-query
Ask questions against the wiki. Synthesizes answers from wiki pages with cross-reference citations.
memory
Unified read-side memory operations including knowledge graph search, session context loading, decision timeline viewing, and Mermaid graph visualization. Subcommands: search, load, history, viz, status. Complements /ork:remember (write-side). Use when searching past decisions, loading context, or visualizing the…
wiki-req
Capture and decompose a concept into atomic, traceable wiki requirements. Clarifies ambiguous requirements, splits them into atomic pieces, and persists them as wiki/requirements/ pages with status tracking.
wiki-digest
Generate a daily or weekly digest of wiki changes — new sources, pages, insights, and gaps.
compact-prep
Ask the agent to prepare for conversation compaction by updating any relevant state and providing guidance for the compaction agent and to kick off the session there after.