Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add gideondk/strata/plugin install 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/consolidate)<a href="https://agentmods.dev/skills/gideondk/strata/consolidate"><img src="https://agentmods.dev/badge/skills/gideondk/strata/consolidate.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.1 | $0.00095 | $0.00523 |
| Opus 5 | $0.00048 | $0.00262 |
| Sonnet 5 | $0.00019 | $0.00105 |
| Haiku 4.5 | $0.00010 | $0.00052 |
Grade A, and why
strata:consolidate 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 6d 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
strata:consolidate
The "graduate durable content out of pr-context" step. Branch dirs that
Have aged past a threshold are scanned for notes worth keeping; those
Get moved to lessons/ with a consolidated_from: breadcrumb.
What gets promoted
A pr-context note is promoted when:
- Its branch dir is older than
--age-days(default 60) - Its
kind:frontmatter is one ofhandoff,decision-draft,review
Other kinds (session, investigation) stay branch-scoped, they're
Transient. Use /strata:archive to retire the whole branch dir when
the PR merged.
How
# Dry-run (default)
"${CLAUDE_PLUGIN_ROOT}/bin/strata" consolidate
# With a different age threshold
"${CLAUDE_PLUGIN_ROOT}/bin/strata" consolidate --age-days 30
# Perform
"${CLAUDE_PLUGIN_ROOT}/bin/strata" consolidate --apply
What it does
For each promoted note:
- Computes
lessons/YYYY-MM-DD-<topic>.mdas the target - Copies the frontmatter forward, adds
consolidated_from:(audit) +consolidated_at:(date) - Deletes the source from pr-context
- Refreshes the FTS index
When to use
- After a wave of PR merges, run dry-run to see what's accumulated
- Monthly hygiene, alongside
/strata:review - Before
/strata:archiveon an old branch — consolidate first, then archive what remains
Don't do
- Don't run on a branch you're still actively working on
- Don't promote
sessionorinvestigationnotes — they're inherently branch-scoped and become noise in lessons/. The script already filters these. - Don't auto-invoke. This is a maintenance action — user-initiated.
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.
- 6d ago First seen · 60 lines · 95 tokens per session scan A e6f0e42cadec
strata:consolidate is a skill published in the GitHub repository gideondk/strata (5 stars, last pushed 1mo ago), licensed MPL-2.0. It adds 95 tokens to every session and 523 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…
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…
mneme-search
Use when the user asks a factual question whose answer might live in the vault. Invokes mnemesearch. Production mnemesearch is FTS5 BM25. The experimental feature-hashed lexical-vector backend is not wired into MCP. KG enrichment is gated to summarize or timeline when full-profile graph state is active.
mneme-prime
Use when the user starts a new task that may have prior vault context worth surfacing. Invokes the mnemeprime MCP tool to build a token-budgeted preamble of recent sessions and topic matches.
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…
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…