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 vakovalskii/ontoship/plugin install ontoshipWrote 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/commands/vakovalskii/ontoship/onto-doc)<a href="https://agentmods.dev/commands/vakovalskii/ontoship/onto-doc"><img src="https://agentmods.dev/badge/commands/vakovalskii/ontoship/onto-doc.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.00070 | $0.00622 |
| Opus 5 | $0.00035 | $0.00311 |
| Sonnet 5 | $0.00014 | $0.00124 |
| Haiku 4.5 | $0.00007 | $0.00062 |
Grade A, and why
onto-doc 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.
What it actually says
Build (or rebuild) the whole OntoShip KB for this repository by fanning out curator agents.
Scope hint: $ARGUMENTS — empty = whole repo; or a subset (e.g. services/api services/billing, or "only reference docs").
Plan
-
Survey the repo — map top-level dirs, services/modules, entry points, build/deploy files, and existing docs. Check current coverage:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/kb-search/gitmark.py stat. -
Decompose into doc areas — one unit of work per area:
- each service/component →
docs/services/<svc>/README.md(node_type: service) - cross-cutting specs (architecture, billing, limits, security) →
docs/reference/(reference) - operational procedures →
docs/ops/(runbook/gotcha) - architectural decisions →
docs/decisions/(decision)
- each service/component →
-
Dispatch curators (fan-out) — for each area spawn a subagent (Task) that follows the
kb-curateskill on that slice only:- search first (don't duplicate); pick
node_type+ correct folder; - write frontmatter (
node_type,title,service,status: active,updated); - add ≥1 typed link to the code it documents (
documents:[src/…]/implemented_by); - add a line to the folder
README.mdindex. Run independent areas in parallel; keep each agent scoped to its area to avoid collisions.
- search first (don't duplicate); pick
-
Entry point + indexes — ensure
CLAUDE.md/AGENTS.mdexists as the entry point,docs/README.mdis the master index, and every folder has a README index. -
Verify & derive —
python3 ${CLAUDE_PLUGIN_ROOT}/skills/kb-search/gitmark.py lint(fix broken links / orphans / missing frontmatter), then... gitmark.py index, then... gitmark.py map -o docs-map.html. -
Report — how many docs created/updated, KB coverage before→after, lint result, and the map path. List any areas that need a human decision.
Principle: md+git is the source of truth; derived (index, graph) is regenerated. Never duplicate — edit existing docs. Keep curator agents scoped so they don't fight over files.
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 · 43 lines · 70 tokens per session scan A adffb43a0b48
onto-doc is a command published in the GitHub repository vakovalskii/ontoship (77 stars, last pushed 12d ago), licensed MIT. It adds 70 tokens to every session and 622 once invoked, about $0.0003 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-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.