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/procedurenpx skills add gideondk/strata --skill proceduregit 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/procedure)<a href="https://agentmods.dev/skills/gideondk/strata/procedure"><img src="https://agentmods.dev/badge/skills/gideondk/strata/procedure.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.00120 | $0.00652 |
| Opus 5 | $0.00060 | $0.00326 |
| Sonnet 5 | $0.00024 | $0.00130 |
| Haiku 4.5 | $0.00012 | $0.00065 |
Grade A, and why
strata:procedure 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
strata:procedure
The "how" notes. Distinct from domain (the "what") and decisions (the "why"). A procedure tells a future engineer (or future Claude) the sequence of Steps to reproduce something.
What goes here
- Onboarding checklists: "first day on this codebase"
- Service templates: "how to add a new bounded context"
- Release runbooks: "shipping a hotfix"
- Test patterns: "writing a new aggregate test"
- Migration recipes: "moving a service to the new pattern"
- Common debugging flows: "what to check when X breaks"
What does NOT belong:
- One-off scripts → keep in code
- Decisions WHY you do it this way →
/strata:decide - What a thing IS →
/strata:domain - "What happened on this branch" →
/strata:save
How
User runs /strata:procedure <title> or you autonomously identify a
Workflow worth capturing. You:
- Compose the procedure as a numbered step list with prerequisites + a verification step.
- Recall first. Call
recall(query="<title>", scope="procedural", layer=1). If a near-duplicate already exists (e.g. "shipping a hotfix" vs "hotfix release runbook"), extend that one instead of adding a second. - Invoke:
cat <<'EOF' | "${CLAUDE_PLUGIN_ROOT}/bin/strata" procedure \
--title "<title>"
# <Title>
## Prerequisites
- ...
## Steps
1. ...
2. ...
## Verify
- ...
## When to use this procedure
<one sentence>
EOF
Lands in <vault>/<repo>/procedural/<slug>.md.
Shape
Always: title, prerequisites, numbered steps, verification, applicability. The verification step is what makes it executable, without it, the Procedure is just narrative.
If a step references code, use backticks (OrderAggregate.cs), those get
Verified against the code graph in /strata:review.
Don't do
- Don't write a procedure for something that happens once. Procedures are for the recurring shape.
- Don't dump command transcripts. Synthesise into "do A, then B, then verify C."
- Don't write a procedure when a decision is what's needed. "We use Postgres" is a decision; "how to add a new Postgres-backed table" is a procedure.
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 · 77 lines · 120 tokens per session scan A 806bd81b09ba
strata:procedure is a skill published in the GitHub repository gideondk/strata (5 stars, last pushed 1mo ago), licensed MPL-2.0. It adds 120 tokens to every session and 652 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
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…
kb
Set up, evolve, or operate a hraness/kb local-first Markdown knowledge base for coding-agent memory. Use when a user asks to design KB conventions or a recurring KB ritual; search or query a KB or Obsidian vault; load or recover repository context, plans, decisions, concepts, backlinks, semantic search, or Git…
memory-forest
Build, validate, index, and query a private local Memory Forest with provenance-aware layers, pointer-first search, and validated root-first retrieval. Use when creating a new forest, checking an existing forest's structure, building its local SQLite index, or retrieving bounded memory trails without exposing full…
memory-forest-retrieve
Integrate a mandatory, metadata-only Memory Forest consultation gate before an agent responds to each non-empty user-authored text turn.
brain
Orient in the user's big-brain second brain and work brain-aware for the rest of the session. Use when the user types /brain, or asks "what am I working on", "what's on my plate", "catch me up", "what's overdue", or at the start of a session about ongoing work. Loads the vault overview, reports it in one screen, and…
capture
Quick-capture a thought, idea, link, or fact into the big-brain second brain's inbox. Use when the user types /capture , or says "note this down", "remember this in my brain", "add to my inbox", "capture this idea". Zero-friction: file it now, organize later.