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/doctor)<a href="https://agentmods.dev/skills/gideondk/strata/doctor"><img src="https://agentmods.dev/badge/skills/gideondk/strata/doctor.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.00108 | $0.00622 |
| Opus 5 | $0.00054 | $0.00311 |
| Sonnet 5 | $0.00022 | $0.00124 |
| Haiku 4.5 | $0.00011 | $0.00062 |
Grade A, and why
strata:doctor 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
strata:doctor
The post-install "is it actually working?" surface. Onboarding's real
friction isn't the install command — it's the silent uncertainty after:
did the venv build, is the vault wired, will semantic search work or
quietly fall back to FTS? doctor answers all of it at once.
How
"${CLAUDE_PLUGIN_ROOT}/bin/strata" doctor
What it checks
| Check | Required? | Failure means |
|---|---|---|
| runtime packages | yes | venv didn't build — pip install -r requirements.txt |
| vault directory | yes | vault_path wrong or not writable |
| repo namespace | yes | not initialised — run /strata:init |
| search index | warn | 0 notes is fine on a fresh vault |
| semantic search | warn | model not ready — recall degrades to FTS5 |
| MCP server | yes | server.py / .mcp.json missing from the install |
| git repo | warn | branch/PR scoping disabled outside a repo |
Exit code is 0 when every required check passes, 1 otherwise.
What you'll see
[strata] doctor — health check for myrepo
✓ runtime packages — 3 required, 2/2 optional present
✓ vault directory — /Users/me/StrataVault
✓ repo namespace — myrepo → ~/StrataVault/myrepo
✓ search index — 142 note(s) indexed (318 KB)
✓ semantic search — embeddings available (hybrid FTS+vector)
✓ MCP server — server.py + .mcp.json present
✓ git repo — branch/PR awareness active
[strata] ✓ healthy — ready to save, decide, and recall
When to use
- Right after
/strata:init, to confirm the runtime is good before the first save / decide / recall. - Whenever recall returns nothing surprising and the user wonders if it's broken (often it's the FTS fallback, which this makes visible).
- As a quick sanity pass after
git pull+/reload-plugins.
Don't do
- Don't fix things silently. Surface each ⚠/✗ with its hint and let the user decide. The point is legibility.
- Don't treat a ⚠ (warn) as failure — optional gaps still leave a working plugin.
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 · 63 lines · 108 tokens per session scan A d8f692c12443
strata:doctor is a skill published in the GitHub repository gideondk/strata (5 stars, last pushed 1mo ago), licensed MPL-2.0. It adds 108 tokens to every session and 622 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
build-test
Run the project's build / typecheck / lint / test commands and emit the build.passing + tests.passing signals devloop convergence reads.
patch-edit
Apply one rewrite-plan step at a time as small reviewable file edits, never rewriting whole files when a localised change suffices.
cvm-ai-doctor
A health-diagnosis workflow for servers, computers, virtual machines, and containers on Linux, macOS, or Windows.
gini-bug-report
File a locally-captured, already-redacted Gini crash report as a GitHub issue, with the user's consent. Reads the pending crash queue and delegates the actual filing to the github-issues skill.
adv-debug
Debug and analyze an ADV.JS project using deterministic checks. Use when validating scripts, resolving missing character or scene references, finding dead branches or orphan scenes, measuring route coverage, inspecting compiled project context, or replaying a failing narrative path.
fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.