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 bmbouter/redhat-agents --skill decision-recordgit clone --depth 1 https://github.com/bmbouter/redhat-agentsWrote 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/bmbouter/redhat-agents/decision-record)<a href="https://agentmods.dev/skills/bmbouter/redhat-agents/decision-record"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/decision-record/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/bmbouter/redhat-agents/decision-record"><img src="https://agentmods.dev/badge/skills/bmbouter/redhat-agents/decision-record.svg" alt="Reviewed on agentmods" width="80" 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.00025 | $0.00474 |
| Opus 5.5 | $0.00010 | $0.00190 |
| Sonnet 5.5 | $0.00005 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
decision-record 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 1mo 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
When to Use
After any significant product decision — feature scoping, priority changes, architectural choices, trade-offs, scope cuts, or direction changes.
Instructions
1. Capture the decision
Ask the PM:
- What was decided? (one clear statement)
- What triggered this decision? (customer feedback, technical constraint, strategic shift)
- What alternatives were considered? (at least 2, ideally 3+)
- Why was this option chosen? (criteria, trade-offs)
- Who was involved? (decision maker, consulted, informed)
- What does this affect? (epics, teams, timelines, customers)
2. Draft the record
## Decision Record: [Decision Title]
**Date**: <date>
**Status**: Decided / Proposed / Superseded
**Decision maker**: [Name/role]
### Context
[What prompted this decision — the problem or question]
### Decision
[Clear statement of what was decided]
### Alternatives Considered
| Option | Pros | Cons |
|--------|------|------|
| **[Chosen option]** | ... | ... |
| [Alternative A] | ... | ... |
| [Alternative B] | ... | ... |
### Rationale
[Why the chosen option won — which criteria mattered most]
### Consequences
- **Epics affected**: [List with links]
- **Timeline impact**: [Acceleration, delay, or neutral]
- **Teams affected**: [Who needs to know]
- **Customer impact**: [Visible change, migration needed, or transparent]
### Stakeholders
| Role | Name | Status |
|------|------|--------|
| Decision maker | ... | Decided |
| Consulted | ... | Agreed / Disagreed |
| Informed | ... | Notified / Pending |
3. Store the record
Ask the PM where to put it:
- As a Jira comment on the relevant epic
- As a Confluence page
- As a local file in the repo
Present for review before posting.
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.
- 1mo ago First seen · 70 lines · 25 tokens per session scan A 0afb3490d899
decision-record is a skill published in the GitHub repository bmbouter/redhat-agents (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 474 once invoked, about $0.0001 per session on Opus 5.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
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…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…