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/export-to-repo)<a href="https://agentmods.dev/skills/gideondk/strata/export-to-repo"><img src="https://agentmods.dev/badge/skills/gideondk/strata/export-to-repo/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/skills/gideondk/strata/export-to-repo"><img src="https://agentmods.dev/badge/skills/gideondk/strata/export-to-repo.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.00112 | $0.00532 |
| Opus 5 | $0.00056 | $0.00266 |
| Sonnet 5 | $0.00022 | $0.00106 |
| Haiku 4.5 | $0.00011 | $0.00053 |
Grade A, and why
strata:export-to-repo 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 10d 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:export-to-repo
The vault is the working store. The repo is the audit anchor. Most decisions Live happily in the vault, fast capture, no PR overhead. But some need to Become part of the codebase's permanent record: regulatory ADRs, decisions Referenced by code, anything that should ship with the repo.
This skill copies one file from the vault into the repo, with a --strict
Lint pass first, so PHI/secrets can't slip across the boundary unnoticed.
Workflow
User runs /strata:export-to-repo decisions/<slug>.md. You:
- Confirm the file path is right (use
recallor/strata:findif unsure). - Run with
--dry-runfirst so the user sees the destination + lint:
"${CLAUDE_PLUGIN_ROOT}/bin/strata" export \
--source decisions/2026-05-20-use-postgres.md \
--preset secrets,pii \
--dry-run
- If clean, re-run without
--dry-run. - The script prints the
git add/git commitcommands. You suggest them to the user; they confirm and run them.
Configuration
--source— required, vault-relative path--dest— repo-relative directory (defaultdocs/adr/)--preset— lint presets (defaultsecrets,pii; addphi-uk/phi-usfor regulated content)--dry-run— show what would happen, don't copy
What it intentionally doesn't do
- Doesn't run
git add/commit/push— those are user decisions. - Doesn't rewrite the file (frontmatter stays as-is).
- Doesn't delete the vault copy. The vault keeps the source of truth; the repo gets a synchronised audit copy.
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.
- 10d ago First seen · 49 lines · 112 tokens per session scan A 93fcaabb4af3
strata:export-to-repo is a skill published in the GitHub repository gideondk/strata (5 stars, last pushed today), licensed MPL-2.0. It adds 112 tokens to every session and 532 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…
shelve
Offload a closed conversation topic (or a whole imported dialog) to the memory shelf as a Markdown episode with a validated digest. Use when a topic is finished, when context grows heavy, before compaction, or when the user asks to shelve/archive part of the conversation. M0 prompt-only version — the agent does the…
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…