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 agentmods add skills/sp-daewoon/chronicle/adrnpx skills add sp-daewoon/chronicle --skill adrgit 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/adr)<a href="https://agentmods.dev/skills/sp-daewoon/chronicle/adr"><img src="https://agentmods.dev/badge/skills/sp-daewoon/chronicle/adr.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 | $0.00076 | $0.00428 |
| Opus 5 | $0.00038 | $0.00214 |
| Sonnet 5 | $0.00015 | $0.00086 |
| Haiku 4.5 | $0.00008 | $0.00043 |
Grade A, and why
adr 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 3d 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
ADR Workflow
Record and manage Architecture Decision Records.
Resolve configuration first
Run the index helper in read mode to learn the ADR directory and current records:
node "${CLAUDE_PLUGIN_ROOT}/scripts/adr-index.mjs"
This prints the current index table (using chronicle.config.json if present, else auto-detected docs/adr / adr/). The next ADR number is max(existing) + 1.
Create a new ADR
- Determine the next number from the index output above.
- Read the template at
${CLAUDE_PLUGIN_ROOT}/templates/adr-template.md. - Fill
{{NUMBER}},{{TITLE}},{{DATE}}(today, from the user/environment — never guess a random date). - Write to
<adr.dir>/<NNNN>-<kebab-title>.md(zero-padded tonumberWidth). - Regenerate the index:
node "${CLAUDE_PLUGIN_ROOT}/scripts/adr-index.mjs" --write
Transition status
Edit the ADR's frontmatter status: (and the ## Status section) to one of: Proposed, Accepted, Deprecated, Superseded, Rejected. When superseding, add Superseded by ADR-NNNN and link both directions. Then re-run adr-index.mjs --write.
Rules
- Numbers only increase; never reuse or renumber.
- One decision per ADR.
- Write the ADR before or as the decision is made, not long after.
- Always regenerate the index after any change.
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.
- 3d ago First seen · 43 lines · 76 tokens per session scan A 7e747455076b
adr is a skill published in the GitHub repository sp-daewoon/chronicle (4 stars, last pushed 3mo ago), licensed MIT. It adds 76 tokens to every session and 428 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
bootstrap
Scaffold or retrofit documentation-led conventions (AGENTS.md, CLAUDE.md, CONVENTIONS.md, ADR catalogue, plan/ queue, agent/ coordination) into a repo. Use when the user asks to "set up conventions", "bootstrap ADRs", "scaffold the documentation-led layout", "add AGENTS.md and a plan queue", or invokes /bootstrap.…
readme
This skill should be used to audit OR elevate the README of a public repository. Trigger with "improve the README", "make the readme high quality", "elevate this readme", "audit the readme", "add badges", "is our README good", or before publishing/releasing a repo. Elevate rebuilds a thin/generic README to a polished…
adr-integration
This skill should be used when the user asks about "ADR integration", "ADR CI/CD", "ADR tooling", "ADR automation", "export ADRs", "ADR documentation site", or needs guidance on integrating ADRs with CI/CD, documentation sites, and other tools.
adr-format-structured-madr
This skill should be used when the user asks about "structured MADR", "structured-madr", "frontmatter ADR", "comprehensive ADR", "auditable ADR", or needs guidance on creating ADRs using the Structured MADR format with YAML frontmatter and audit sections.
adr-decision-drivers
This skill should be used when the user asks about "decision drivers", "architectural forces", "quality attributes", "how to identify trade-offs", "non-functional requirements for ADRs", or needs help identifying, documenting, and weighing the forces that influence architectural decisions.
adr-format-madr
This skill should be used when the user asks about "MADR format", "MADR template", "Markdown Architectural Decision Records", "MADR 4.0", "MADR sections", or needs guidance on creating ADRs using the MADR (Markdown Architectural Decision Records) format.