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 skills add majiayu000/spellbook --skill skill-ecosystem-doctorgit clone --depth 1 https://github.com/majiayu000/spellbookWrote 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/majiayu000/spellbook/skill-ecosystem-doctor)<a href="https://agentmods.dev/skills/majiayu000/spellbook/skill-ecosystem-doctor"><img src="https://agentmods.dev/badge/skills/majiayu000/spellbook/skill-ecosystem-doctor/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/majiayu000/spellbook/skill-ecosystem-doctor"><img src="https://agentmods.dev/badge/skills/majiayu000/spellbook/skill-ecosystem-doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 252 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- medium Rogue Agent · line 73 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Output Handling · line 208 Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.Fix: Set explicit limits on output length, generation count, and rate. Use max_tokens and truncation to prevent unbounded output.
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.00075 | $0.02480 |
| Opus 5 | $0.00037 | $0.01240 |
| Sonnet 5 | $0.00015 | $0.00496 |
| Haiku 4.5 | $0.00007 | $0.00248 |
Grade A, and why
skill-ecosystem-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 8d 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 — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Ecosystem Doctor
Treat the local Skill collection as a governed software supply chain. Audit first, plan repairs from evidence, apply only authorized changes, and finish with fresh cross-runtime verification and a durable handoff.
This workflow is at skill maturity, not unattended automation maturity. Do
not schedule or silently apply repairs.
Trigger boundary
Questions such as “Did Studio load or start these Skills?” belong to Studio's own configuration, projections, and runtime inventory. Inspect that project/runtime directly. Invoke this Doctor only when the user explicitly asks for cross-runtime or cross-scope ownership, projection, exposure, lifecycle, or repair governance.
Select the mode
| User intent | Mode | Routing |
|---|---|---|
| Inspect, review, inventory, or diagnose | audit |
execute_direct; read-only |
| Explain what should change | plan |
plan_first; no mutations |
| Fix, unify, quarantine, or retire | repair |
plan_first; explicit scope and rollback |
| Recheck an existing governance file | verify |
execute_direct; read-only |
| Rotate credentials, rewrite history, push, publish, or change remotes | external action | clarify_first unless the current request grants that exact action |
If the request mixes modes, run audit before repair. Do not infer repair
authorization from a request to inspect or diagnose.
Operating Contract
- Direct actions: read-only discovery, deterministic audits, report drafts, and local validation.
- Escalate before: destructive changes, credential actions, history rewriting, remote publication, or any mutation not named by the current repair request.
- Evidence-backed pushback: challenge a proposed source, deletion, or completion claim only with paths, state queries, tests, ownership records, or a concrete data-loss or security risk.
- Feedback loop: promote repeated false positives, runtime-layout changes, and manual recovery steps into checks, fixtures, references, or evals.
What ships with it
20 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 354 B
- assets/remediation-log-template.md 1.1 KB
- assets/skill-governance.example.json 1.2 KB
- evals/evals.json 5.1 KB
- references/governance-schema.md 8.3 KB
- references/lifecycle-drift.md 2.1 KB
- references/remediation-playbook.md 3.7 KB
- references/runtime-contracts.md 4.3 KB
- requirements.txt 7 B
- scripts/ecosystem_checks.py 14 KB runs code
- scripts/ecosystem_doctor.py 2.1 KB runs code
- scripts/ecosystem_exposure.py 7.0 KB runs code
- scripts/ecosystem_governance.py 12 KB runs code
- scripts/ecosystem_legacy.py 12 KB runs code
- scripts/ecosystem_model.py 8.6 KB runs code
- scripts/ecosystem_plugins.py 2.6 KB runs code
- scripts/ecosystem_reconcile.py 32 KB runs code
- scripts/ecosystem_runtimes.py 4.6 KB runs code
- scripts/ecosystem_scans.py 25 KB runs code
- scripts/ecosystem_split.py 8.5 KB runs code
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.
- 8d ago First seen · 255 lines · 75 tokens per session scan A 8b35f63f9fe8
skill-ecosystem-doctor is a skill published in the GitHub repository majiayu000/spellbook (278 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 2,480 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
pneuma-session
Instructions for renaming an active Pneuma session and replacing its default preview with a useful title and summary. A Pneuma session is one work area inside a larger project.
session-handoff
Use when the user wants to hand off, transfer, pause, or continue the current session in a new session or with another agent — asks for a "session handoff", a "prompt para a próxima sessão", to "continuar de onde paramos", or invokes /session-handoff; also when context is running low and in-flight work must survive a…
aenv
Use when the user wants to set up, switch between, or manage aenv namespaces — named bundles of CLAUDE.md, skills, MCP entries, and other AI-coding-harness config — in a project OR globally across $HOME. Triggers include aenv … mentioned directly, "switch namespace/profile", "activate/deactivate", "create/snapshot a…
cao-session-management
Interact with CAO (CLI Agent Orchestrator) — launch multi-agent sessions, check status, send follow-up instructions, unblock stuck terminals, or shut down sessions. Use when working with CAO sessions in any capacity.
mulmoterminal-keys
Bind keyboard shortcuts and fix keyboard/clipboard behaviour in MulmoTerminal. Writes keymap, which Settings cannot set at all — its Keyboard shortcuts section is read-only, listing every action bound or not plus a send row. Explains copyOnSelect, questionPaneEnabled and terminalSubmit, which have their own Settings…
tokf-discover
Find missed token savings by scanning AI coding session files for commands that ran without tokf filtering.