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/kensaurus/cursor-kenji/docs-adrnpx skills add kensaurus/cursor-kenji --skill docs-adrgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/docs-adr)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/docs-adr"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/docs-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.00066 | $0.01705 |
| Opus 5 | $0.00033 | $0.00852 |
| Sonnet 5 | $0.00013 | $0.00341 |
| Haiku 4.5 | $0.00007 | $0.00170 |
Grade A, and why
docs-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 yesterday.
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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
docs-adr — Decision memory the next session can load
Degree of freedom: MIXED — T1 is the priority. What to record
[HIGH freedom]; format, supersede-not-edit, and present-backfill-first
[LOW freedom — run exactly].
Install and maintain the repo's decision memory. Code shows what was decided; nothing shows why, or what was rejected — so every new agent session is free to "improve" its way back to an alternative you already ruled out. Re-litigated decisions are the slowest form of drift. An ADR makes the decision durable and its reversal deliberate.
This skill vs neighbors
| Skill | Owns |
|---|---|
| docs-adr (this) | Why we chose X; rejected alternatives; INDEX.md |
plan-docs-sync |
Docs vs what the code is — not why |
handoff |
Session state for the next chat — not permanent decisions |
docs-writer |
Tutorials / README prose |
enhance-arch-boundaries |
Mechanical layering; this records the model |
workflow-housekeep |
Periodic index / status sweep |
housekeep-backlog |
Parked-work register (BACKLOG.md), not decisions |
How to reason
- Observe — the decision, the rejected alternative, who already tried to reverse it
- Interpret — would a fresh agent "improve" back to the rejected option?
- Classify — ADR / not-an-ADR (linter already enforces, routine impl)
- Severity — load-bearing unusual choice first
Worked example
Observe: agent PR re-proposes Zustand; repo uses React context for session by choice; no ADR. Interpret: the rejection is oral memory — the next session will retry. Classify: ADR — stack choice with a rejected alternative. Write: "We use React context for session. Rejected Zustand: duplicate store vs server session." Present the backfill list before writing files.
Phase 0 — Set up the system (once per repo) [LOW freedom — INDEX.md + statuses]
docs/adr/NNNN-short-title.md, numbered sequentially, plusdocs/adr/INDEX.md— one line per ADR (NNNN | title | status | one-line decision). The index is the agent-facing surface: small enough to load every session.- Reference the index from agent rules: "Before proposing a change to
architecture, dependencies, conventions, or data models, read
docs/adr/INDEX.md; do not contradict an Accepted ADR without flagging it explicitly to the user." - Statuses: Proposed → Accepted → Superseded by NNNN / Deprecated. Never edit an Accepted ADR's decision — supersede it with a new one that links back. History is the point.
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.
- yesterday First seen · 169 lines · 66 tokens per session scan A 530fc9b7965e
docs-adr is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 7d ago), licensed MIT. It adds 66 tokens to every session and 1,705 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
project-docs-management
项目结构化知识库初始化，基于渐进式披露原则从零搭建AGENTS.md、架构.md和文档目录。仅用于首次建立知识库，后续维护和文档整理请使用 doc-gardener 技能。当用户提到"建立知识库""初始化文档""搭建文档结构"时使用。.
apple-notes-sync
将 Mac 备忘录同步到工作区并加入向量索引，实现语义搜索。当用户说"同步备忘录"、"把备忘录加入记忆"、或想搜索备忘录内容时使用。.
checkpoint
Save a session checkpoint — what was done, what's next, any blockers.
resume
Resume from last checkpoint — load full context and continue where you left off.
note
Quick note — save a decision, observation, or thought to persistent memory.
recallium-guidance
Use when you have access to Recallium MCP tools. Provides guidance on memory storage, search, and knowledge management. CRITICAL - invoke the MCP tool recallium at session start, store memories after EVERY substantive interaction, and honor global rules.