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 agentmods add commands/hiromaily/docs-ssot/migrategit clone --depth 1 https://github.com/hiromaily/docs-ssotWrote 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/hiromaily/docs-ssot/migrate)<a href="https://agentmods.dev/commands/hiromaily/docs-ssot/migrate"><img src="https://agentmods.dev/badge/commands/hiromaily/docs-ssot/migrate.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 | $0.00000 | $0.00938 |
| Opus 5 | $0.00000 | $0.00469 |
| Sonnet 5 | $0.00000 | $0.00188 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
migrate 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 4d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
docs-ssot migrate
Decompose existing monolithic Markdown files (e.g., README.md, CLAUDE.md) into the docs-ssot section structure.
docs-ssot migrate [files...] [flags]
This is the primary adoption command. It takes existing documentation files and converts them into modular, reusable sections with template files that reproduce the original document structure via @include directives.
What it does
- Splits each input file by H2 headings into candidate sections
- Categorises sections into directories (
project/,development/,architecture/,reference/,product/,misc/) based on heading keyword heuristics - Detects duplicates across input files using TF-IDF cosine similarity (reuses the
checkcommand's engine) - Creates section files under
template/sections/<category>/<slug>.md - Creates template files under
template/pages/<name>.tpl.mdwith@includedirectives - Creates
docsgen.yamlif it does not already exist - Verifies round-trip by running
buildand comparing output against originals
Section categorisation
Sections are assigned to categories based on heading keywords:
| Heading keywords | Category |
|---|---|
| Architecture, Design, System, Pipeline | architecture/ |
| Overview, About, Introduction, Background | project/ |
| Install, Setup, Getting Started, Prerequisites | development/ |
| Test, Testing, CI | development/ |
| Lint, Format, Code Quality | development/ |
| Contributing, Contribute | development/ |
| API, Commands, CLI, Reference | reference/ |
| License, Changelog, Roadmap | project/ |
| FAQ, Troubleshooting | product/ |
| (fallback) | misc/ |
Duplicate handling
When the same content appears in multiple input files:
- TF-IDF cosine similarity is computed between all cross-file section pairs
- Pairs scoring above the threshold are merged into a single section file
- Both templates reference the shared section via
@include
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.
- 4d ago First seen · 117 lines · 0 tokens per session scan A 8d651fb054f7
migrate is a command published in the GitHub repository hiromaily/docs-ssot (2 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 938 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.