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/gideondk/strata/decidenpx skills add gideondk/strata --skill decidegit clone --depth 1 https://github.com/gideondk/strataWrote 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/gideondk/strata/decide)<a href="https://agentmods.dev/skills/gideondk/strata/decide"><img src="https://agentmods.dev/badge/skills/gideondk/strata/decide.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.00092 | $0.01494 |
| Opus 5 | $0.00046 | $0.00747 |
| Sonnet 5 | $0.00018 | $0.00299 |
| Haiku 4.5 | $0.00009 | $0.00149 |
Grade A, and why
strata:decide 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 3d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
strata:decide
ADRs (Architectural Decision Records) capture why something is the way it is. They're durable team memory, code rots, ADRs explain it.
When to use
- A choice between two reasonable options where future readers will wonder why.
- A constraint discovered the hard way that should be remembered.
- A trade-off that locks something in.
Not for: routine implementation choices, style preferences, or anything fully Explained by the code itself.
How
User runs /strata:decide <title>. You:
- Draft the body using the MADR sections: Context, Decision, Consequences, Alternatives considered. Be concrete. No fluff.
- Pick the status:
proposed(default, opens a discussion),accepted(the team has agreed), orsuperseded/rejected/deprecated. - Recall before you write — check for an existing decision first. Run the dedup precheck so you don't fork a parallel ADR for a choice that's already recorded (the "agents battling on ADRs" failure):
"${CLAUDE_PLUGIN_ROOT}/bin/strata" decide \
--title "<title>" --check-only <<'STRATA_ADR'
<the body you drafted>
STRATA_ADR
It prints JSON {recommendation, candidates} and writes nothing to the
vault (it may refresh the disposable index cache). Run it on its own —
--check-only is a no-op alongside --supersedes/--no-dedup. Adjudicate:
clear→ no overlap; proceed to step 4 (ADD).warn/block→ read the candidate(s) and decide, surfacing it to the user:- UPDATE — same decision, just refined → edit that note, don't create a new one.
- SUPERSEDE — this replaces an earlier decision → write with
--supersedes <slug>(see below). - NO-OP — already captured → write nothing; tell the user.
- ADD — genuinely distinct despite the overlap → write with
--ack-new(ablockrefuses to write without it).
Use the candidates to ground the draft. Even on clear, the precheck
returns the nearest existing notes. Before writing, skim the top 2-3: match
their section structure, reuse house terminology, and [[wikilink]] the
genuinely related ones in your body. A well-linked draft beats an orphan.
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.
- 3d ago First seen · 128 lines · 92 tokens per session scan A 1e484b7d5049
strata:decide is a skill published in the GitHub repository gideondk/strata (5 stars, last pushed 1mo ago), licensed MPL-2.0. It adds 92 tokens to every session and 1,494 once invoked, about $0.0005 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
my-wiki
Manage local OKF-compatible Markdown My Wiki vaults with an AI agent. Use for capturing webpages, PDFs, Office documents, notes, images, folders, and ZIP bundles as References; maintaining Reference-to-Concept evidence links; searching or answering from a vault; checking or repairing vault health; switching among…
save-to-favorites
The single complete Pickoo workflow for new Xiaohongshu, WeChat, Douyin, Bilibili, Xiaoyuzhou, podcast, music, article/blog, or general web links. Use for 收藏、保存、收录、抓取、归档、拆解、分析、OCR、ASR or 完整处理 from Codex, WorkBuddy, Hermes, Claude, or Claudian. It owns intake and the complete downstream workflow; obsolete standalone…
asset-review-agent
Independently review source-extracted quote, viewpoint, hook, and structure candidates. Image and shot assets are outside automatic review and enter only after explicit user interaction.
phase-orchestrator
Orchestrates phase-based implementation plans using the host's todo tracker and subagents for implementation, review, validation, default phase commits, plan finalization, and a final end-to-end review. Delegates work through the companion phase-implementer, phase-reviewer, and phase-final-reviewer skills and consumes…
answer-processing
Use whenever the user uploads a hand-written or scanned answer PDF to be graded against a reference solution. Converts answer PDFs in answers/.pdf to markdown in answers/converted/.md using the pdf skill (OCR as needed), then performs strategy-based grading against converted/solutions/.md or quizzes/answers.md.…
course-builder
Use whenever the user wants to ingest a new course's materials (lecture notes, textbook chapters, HW problems, HW solutions) and build the course-specific knowledge base — patterns.md (recurring solution techniques), coverage.md (HW-to-section map with 🔥 exam tiers + ⚠weak flags), and summary.md (topic tree). Invoked…