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 commands/scarrillo/release/decisionsgit clone --depth 1 https://github.com/scarrillo/releaseWhat 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.00007 | $0.00674 |
| Opus 5 | $0.00003 | $0.00337 |
| Sonnet 5 | $0.00001 | $0.00135 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
decisions 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decisions Document Generator
Capture decisions and proposals from the current session for future reference. Includes both implemented decisions and proposals still under consideration.
Model: Uses the model configured in release-plugin.model (see /release:changelog for model selection).
How to Run
- Standalone: Run
/decisionsdirectly at any point to capture decisions from the current session - From /release:changelog: After generating a changelog, you'll be prompted to run this command
When to Use
- After discussing architectural approaches
- When a decision was made (implemented or not)
- When proposals were explored but deferred
- After comparing solutions or libraries
- When trade-offs were evaluated
- After a research or exploration session (even without code changes)
Instructions
-
Review current session for:
- Decisions made (with rationale)
- Proposals discussed (implemented or not)
- Approaches compared
- Trade-offs evaluated
- Ideas deferred for later
-
Capture regardless of implementation status:
- Implemented → document the decision and link to changelog
- Not implemented → document as proposal for future review
- Rejected → document why it was rejected (valuable context)
-
Organize by topic for easy future reference
Output Location
If decisions.md doesn't exist, ask the user: "Where should I create the decisions document?"
- Project root (
./decisions.md) - Documentation folder (
./docs/decisions.md) - Same location as changelog (if it exists)
- Custom location (let user specify)
If decisions.md already exists, use its current location.
If file exists: Prepend new entries after the # Decisions & Proposals header (newest entries at top). Read existing content first to avoid duplicates.
Output Format
Structure:
# Decisions & Proposals
## [Topic/Feature Area] - YYYY-MM-DD
### Status: [Implemented | Proposed | Rejected | Deferred]
### Context
[What problem or question prompted this decision/proposal?]
### Proposal
[What was proposed or decided?]
### Options Considered
1. **[Option A]**: [Brief description]
- Pros: [advantages]
- Cons: [disadvantages]
2. **[Option B]**: [Brief description]
- Pros: [advantages]
- Cons: [disadvantages]
### Decision
[What was decided, or "Pending review" if still a proposal]
### Rationale
[Why this approach was chosen/proposed]
### Trade-offs Accepted
[What compromises come with this decision]
### References
- [Links to docs, samples, related PRs]
---
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 · 105 lines · 7 tokens per session scan A 9077593d7273
decisions is a command published in the GitHub repository scarrillo/release (9 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 674 once invoked, about $0.0000 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.