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.
git 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/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/commands/hiromaily/docs-ssot/migrate"><img src="https://agentmods.dev/badge/commands/hiromaily/docs-ssot/migrate.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.00000 | $0.00938 |
| Opus 5.5 | $0.00000 | $0.00375 |
| Sonnet 5.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 2mo 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.
- 2mo 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 7mo 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.
migrate compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| migratehiromaily/docs-ssot | Command | 2 | 7mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |