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/migrate-fromgit 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-from)<a href="https://agentmods.dev/commands/hiromaily/docs-ssot/migrate-from"><img src="https://agentmods.dev/badge/commands/hiromaily/docs-ssot/migrate-from.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.00000 | $0.00606 |
| Opus 5 | $0.00000 | $0.00303 |
| Sonnet 5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
migrate-from 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 5d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent-aware migration (--from)
With --from, migrate scans AI tool configuration files (rules, skills, commands, subagents) from the specified tool and generates SSOT sections with per-tool templates for the target tools.
docs-ssot migrate --from <tool> [--to <tools>] [flags]
What it does
- Scans the source tool's configuration directory for rules, skills, commands, and subagents
- Strips frontmatter from source files and shifts H1→H2 headings
- Creates section files under
template/sections/ai/<type>/<slug>.md - Generates templates for each target tool with appropriate frontmatter
- Updates
docsgen.yamlwith new build targets - Verifies round-trip by building and comparing against originals
Flags
| Flag | Default | Description |
|---|---|---|
--from |
(required) | Source AI tool to migrate from (claude, cursor, copilot) |
--to |
all except --from |
Target tools, comma-separated (cursor,copilot,codex) |
--convert-commands |
false |
Convert legacy commands to skills during migration |
--infer-globs |
false |
Infer path-gated globs from rule slug names |
--dry-run |
false |
Print the migration plan without writing files |
Examples
Migrate Claude configs to all other tools:
docs-ssot migrate --from claude
Migrate to specific tools only:
docs-ssot migrate --from claude --to cursor,codex
Preview migration plan:
docs-ssot migrate --from claude --dry-run
Migrate with path inference and command conversion:
docs-ssot migrate --from claude --to cursor --infer-globs --convert-commands
Combine agent and file migration:
docs-ssot migrate --from claude --to cursor README.md CLAUDE.md
Output
Detected source tool: claude (5 files)
Target tools: cursor, copilot, codex
Creating sections:
template/sections/ai/rules/architecture.md
template/sections/ai/rules/testing.md
template/sections/ai/skills/deploy.md
template/sections/ai/subagents/critic.md
template/sections/ai/subagents/debugger.md
Creating templates (3 tools × 5 files):
cursor: 5 templates
copilot: 5 templates
codex: 4 templates
Updated docsgen.yaml (14 new targets)
Verifying round-trip...
Round-trip verification: OK
Agent migration complete.
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.
- 5d ago First seen · 83 lines · 0 tokens per session scan A 6fb08ee56bac
migrate-from 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 606 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
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.