Borrowing it
Nothing to install: this file belongs to charlesapetersen/Archive-Suite. 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/charlesapetersen/Archive-Suite/main/CLAUDE.mdgit clone --depth 1 https://github.com/charlesapetersen/Archive-SuiteWrote 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/instructions/charlesapetersen/archive-suite/claude-md)<a href="https://agentmods.dev/instructions/charlesapetersen/archive-suite/claude-md"><img src="https://agentmods.dev/badge/instructions/charlesapetersen/archive-suite/claude-md/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/instructions/charlesapetersen/archive-suite/claude-md"><img src="https://agentmods.dev/badge/instructions/charlesapetersen/archive-suite/claude-md.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.07075 | $0.07075 |
| Opus 5 | $0.03537 | $0.03537 |
| Sonnet 5 | $0.01415 | $0.01415 |
| Haiku 4.5 | $0.00707 | $0.00707 |
Grade A, and why
Archive-Suite CLAUDE.md 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 8d 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 — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Archive Suite — Umbrella Project Guide
Three native macOS apps in one monorepo: Archive Processor (capture · OCR · tag),
Archive Reader (find · read · triage), and Archive Notes (provenance‑first note‑taking from
archival sources). This file is the umbrella guide — repo‑wide conventions, the shared contract, and
the release process. Each app's own CLAUDE.md stays authoritative for that app; read it before
working inside a subdirectory:
ArchiveProcessor/CLAUDE.md— the Processor + its iOS/Android capture companions.ArchiveReader/CLAUDE.md— the Reader (incl. its bulletproof file‑safety Core Directive).ArchiveNotes/CLAUDE.md— Notes (provenance‑first notes + extracts from archival PDFs).
🛑 THE DAEMON REPORT IS A WALKTHROUGH, NOT A DOCUMENT — read this before answering any request for it
Trigger phrases: "daemon report", "the report", "morning review" (the old name), "anything for me?", "anything I need to decide?", "what needs my eye?", "walk me through it". Any of these means run the walkthrough below. This section exists because sessions kept getting it wrong in the same two ways, and the owner had to correct it every time.
What the owner wants, exactly: to be walked through each open decision, ONE AT A TIME, waiting for his answer before moving to the next. It is a conversation he steers. That is the whole deliverable.
❌ Do NOT do any of these — each one has actually happened and is a failure, not a variation:
- ❌ Do not write a new entry into the plan. Being asked for the report is not a cue to author one. Nothing is added to any doc during the walkthrough.
- ❌ Do not dump a summary of everything that happened, however well organised. A recap is not a report.
- ❌ Do not batch the decisions into one message with a numbered list and a single "what do you think?". One decision per message. Stop. Wait.
- ❌ Do not re-raise settled items. Anything under a
### ✅ … walkthroughheading, or inSUITE_TODO.md→ "⛔ DECLINED — settled, do NOT re-raise", is closed. Reopening it wastes his time. - ❌ Do not present non-decisions as decisions. "Worth your eye, nothing blocking" is a mention, not a step. Fold those into one short block at the end, after the real decisions are done.
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.
- 8d ago First seen · 330 lines · 7,075 tokens per session scan A 10fd9cf3fe5c
Archive-Suite CLAUDE.md is an instructions file published in the GitHub repository charlesapetersen/Archive-Suite (3 stars, last pushed 3d ago), licensed MIT. It adds 7,075 tokens to every session, about $0.0354 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.