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.
npx skills add sp-daewoon/chronicle --skill claude-mdgit clone --depth 1 https://github.com/sp-daewoon/chronicleWrote 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/skills/sp-daewoon/chronicle/claude-md)<a href="https://agentmods.dev/skills/sp-daewoon/chronicle/claude-md"><img src="https://agentmods.dev/badge/skills/sp-daewoon/chronicle/claude-md.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.00072 | $0.00347 |
| Opus 5 | $0.00036 | $0.00173 |
| Sonnet 5 | $0.00014 | $0.00069 |
| Haiku 4.5 | $0.00007 | $0.00035 |
Grade A, and why
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 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
CLAUDE.md Maintenance Workflow
Keep an existing CLAUDE.md accurate and lean. This is for ongoing upkeep — use the built-in /init for first creation.
Process
- Read the current
CLAUDE.md. - Compare against reality: recent commits, changed build commands, new/removed modules, updated conventions, new architecture decisions (check the ADR directory).
- Update only the affected sections. Do not rewrite untouched sections.
- Prune: remove stale instructions, merge duplicates, and keep each section tight. If a section has grown long, tighten it rather than letting it sprawl.
- Preserve the user's voice and structure — you are maintaining their file, not replacing it.
What to check for drift
- Build / test / lint commands that changed
- Module or directory structure changes
- New conventions or rules the team adopted
- Architecture decisions recorded as ADRs that belong in the high-level guidance
- Anything now contradicted by the actual codebase
Rules
- Never blow away existing content wholesale — edit surgically.
- Keep it scannable; CLAUDE.md is loaded into every session, so brevity matters.
- If something is already obvious from the code or another doc, don't duplicate it here.
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 · 32 lines · 72 tokens per session scan A faacea5e2e5c
claude-md is a skill published in the GitHub repository sp-daewoon/chronicle (4 stars, last pushed 3mo ago), licensed MIT. It adds 72 tokens to every session and 347 once invoked, about $0.0004 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 skills, from other repositories
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.
ecto-patterns
Ecto patterns — schemas, changesets, queries, migrations, Multi, associations, preloads, upserts. Use when editing Repo calls, Ecto.Query, or schema fields. Skip for Ash.