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.
git clone --depth 1 https://github.com/jabrena/plinthWrote 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/commands/jabrena/plinth/create-adr)<a href="https://agentmods.dev/commands/jabrena/plinth/create-adr"><img src="https://agentmods.dev/badge/commands/jabrena/plinth/create-adr/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/commands/jabrena/plinth/create-adr"><img src="https://agentmods.dev/badge/commands/jabrena/plinth/create-adr.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.00010 | $0.00320 |
| Opus 5.5 | $0.00004 | $0.00128 |
| Sonnet 5.5 | $0.00002 | $0.00064 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
create-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 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
create-adr
Record an important architectural decision, its context, alternatives, and consequences.
Usage
/create-adr <decision-source> [<adr-type>]
Accepted Inputs
- Approved design exploration, issue, specification, or implementation plan
- Existing architecture constraints and related ADRs
- Optional ADR type: general, functional requirements, or non-functional requirements
Owning Agent
@plinth-architect
Associated Skills
030-architecture-adr-general031-architecture-adr-functional-requirements032-architecture-adr-non-functional-requirements
Workflow
- Confirm the decision scope and select the appropriate ADR skill.
- Gather context, constraints, considered alternatives, and consequences.
- Draft the ADR using the repository convention.
- Check consistency with related issues, designs, specifications, and ADRs.
- Present the ADR for approval before finalizing it.
Output
- One repository-compliant ADR
- Decision status, rationale, alternatives, and consequences
- Links to relevant source artifacts
Safeguards
- Do not create an ADR for a decision that has not been made.
- Do not invent alternatives or constraints.
- Do not modify unrelated ADRs.
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 · 57 lines · 10 tokens per session scan A 9105f41a79be
create-adr is a command published in the GitHub repository jabrena/plinth (451 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 320 once invoked, about $0.0000 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-30.
Other commands, from other repositories
epic-plan
Run /epic-plan — see .claude/commands/epic-plan.md for the authoritative spec.
prd
Use when writing a PRD or business case — is this worth building, for whom, at what priority (Google/Amazon/Stripe methodologies).
idea
Use when exploring a new idea — validates demand, analyzes competitors, and checks for pseudo-requirements before writing specs.
start
Run the shorts pipeline across long-lived tmux panes. /start for a fresh run, or /start to reuse an already-ingested video. Each phase shows its progress in the foreground; tmux attach -t to inspect any phase live.
resolve-review.body
$ARGUMENTS.
checklist
Generate a custom checklist for the current feature based on user requirements.