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/rust-works/succinctly/update-adr-inventorynpx skills add rust-works/succinctly --skill update-adr-inventorygit clone --depth 1 https://github.com/rust-works/succinctlyWrote 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/rust-works/succinctly/update-adr-inventory)<a href="https://agentmods.dev/skills/rust-works/succinctly/update-adr-inventory"><img src="https://agentmods.dev/badge/skills/rust-works/succinctly/update-adr-inventory.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.00054 | $0.00730 |
| Opus 5 | $0.00027 | $0.00365 |
| Sonnet 5 | $0.00011 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
update-adr-inventory 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 4d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update ADR Inventory
Rebuild the inventory table in docs/adrs/README.md so it reflects the current
set of ADR files and their metadata.
Critical: Minimise diff noise
Only touch rows that actually changed. When adding a new ADR, append a row matching the existing column widths — do NOT reformat the header, separator, or unchanged data rows. When updating an ADR's status or title, edit only that row's cell content and pad to match the existing column width. The goal is a minimal, reviewable git diff.
Procedure
-
Read the current inventory. Read
docs/adrs/README.mdand parse the existing table to understand current column widths and which ADRs are already listed (with their status and title). -
Find all ADR files. Glob for
docs/adrs/adr-*.md(excludeREADME.md). Sort results in natural numeric order by ADR number. -
Extract metadata from each ADR file. For every file, read the first ~10 lines and extract:
- ADR number and title from the level-1 heading:
# ADR-NNNN: Title - Status from the
## Statussection (the first non-empty line after## Status)
- ADR number and title from the level-1 heading:
-
Determine the date. Use git to get the author date of the commit that first introduced the file:
git log --diff-filter=A --follow --format="%as" -- <file> | tail -1If the file is untracked (no git history), use today's date.
-
Map status text to the table format. Normalise the raw status string (strip any existing emoji) and apply the project's status legend:
Raw (case-insensitive) Table display Proposed 🟡 Proposed Accepted ✅ Accepted Deprecated ❌ Deprecated Superseded 🔄 Superseded If the status does not match any of the above, use the raw text as-is.
-
Compare and apply minimal edits.
- New ADRs: Append a row, padding each cell to match the existing column widths (right-pad with spaces). Do not alter the header or separator rows unless the new content exceeds an existing column width.
- Changed status/title: Edit only the affected cell(s) in the existing row, adjusting padding to maintain alignment.
- Removed ADRs: Delete only that row.
- No changes: Do nothing — do not rewrite the table.
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.
- 4d ago First seen · 69 lines · 54 tokens per session scan A e12f20145198
update-adr-inventory is a skill published in the GitHub repository rust-works/succinctly (52 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 730 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…