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 jeet129/praxis --skill adr-decision-recordsgit clone --depth 1 https://github.com/jeet129/praxisWrote 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/jeet129/praxis/adr-decision-records)<a href="https://agentmods.dev/skills/jeet129/praxis/adr-decision-records"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/adr-decision-records/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/skills/jeet129/praxis/adr-decision-records"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/adr-decision-records.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00125 | $0.02382 |
| Opus 5 | $0.00063 | $0.01191 |
| Sonnet 5 | $0.00025 | $0.00476 |
| Haiku 4.5 | $0.00013 | $0.00238 |
Grade A, and why
adr-decision-records 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 12d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADR — Architecture Decision Records
capability: foundation
domain: cross-cutting
state: active
dependencies:
- project-memory
triggers:
- "making an architecture decision"
- "choosing between technology options"
- "accepting a risk explicitly"
- "waiving a security finding"
- "deprecating a skill, library, or pattern"
- "superseding a prior decision"
- "documenting a Challenger objection override (governance)"
outputs:
- ADR file (.project/decision/adr-NNNN-{slug}.md)
- INDEX entry (added via project-memory + memory-management)
consumers:
- solution-architect
- architecture-challenger
- all role agents (any agent can author an ADR)
- memory-management (indexes ADRs)
references: []
The standard format and lifecycle for the team's decision memory. Every significant decision becomes an ADR. The format is small, opinionated, and the only sanctioned way to record decisions — no scattered Slack messages, no design-doc-then-forgotten, no folklore.
When to write an ADR
An ADR is required for any decision that:
- Changes the architecture — chosen pattern, new bounded context, new integration, new persistence store.
- Selects a technology or vendor — framework, library, managed service, cloud region.
- Accepts a risk or waives a control — Challenger objection override, security finding waiver, NFR target relaxation.
- Deprecates or supersedes — sunsetting a library, retiring a pattern, replacing a service.
- Establishes a project-local convention — overrides to
engineering-standards, naming or layout rules specific to this codebase.
An ADR is not required for trivial decisions (choice of variable name, ordering of arguments, etc.). Test: would a future engineer asking "why did we do this?" benefit from an explanation? If yes, ADR.
The template
ADRs are short. Aim for under 250 lines. Filenames are adr-NNNN-{kebab-case-slug}.md with sequential numbering across the project.
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.
- 12d ago First seen · 216 lines · 125 tokens per session scan A 13e8d92e0b04
adr-decision-records is a skill published in the GitHub repository jeet129/praxis (7 stars, last pushed 8d ago), licensed MIT. It adds 125 tokens to every session and 2,382 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…