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/check)<a href="https://agentmods.dev/commands/hiromaily/docs-ssot/check"><img src="https://agentmods.dev/badge/commands/hiromaily/docs-ssot/check/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/check"><img src="https://agentmods.dev/badge/commands/hiromaily/docs-ssot/check.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.00449 |
| Opus 5.5 | $0.00000 | $0.00180 |
| Sonnet 5.5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
check 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.
What it actually says
docs-ssot check
Check docs for SSOT violations by detecting near-duplicate sections across Markdown files.
docs-ssot check [flags]
Uses TF-IDF cosine similarity to compare sections at the specified heading level. Sections scoring above the threshold are reported as potential SSOT violations — places where the same information exists in multiple source files.
Flags
| Flag | Default | Description |
|---|---|---|
--root |
docs |
Root directory to scan for Markdown files |
--threshold |
0.82 |
Similarity cutoff (0.0–1.0); pairs above this score are reported |
--min-chars |
120 |
Minimum character count for a section to be included in comparison |
--section-level |
2 |
Heading level used as section boundary (1–6) |
--format |
text |
Output format: text or json |
--exclude |
— | Exclude path pattern (repeatable) |
Examples
Basic check with default settings:
docs-ssot check
Lower threshold to catch more candidates:
docs-ssot check --threshold 0.75
Compare at H3 level, exclude changelogs, output JSON:
docs-ssot check --section-level 3 --exclude docs/changelog/** --format json
Output
Text output (one block per similar pair):
score=0.891
A: docs/auth/overview.md [API > Authentication]
B: docs/setup/login.md [Setup > Authentication]
A title: Authentication
B title: Authentication
A snippet: Authentication tokens must be refreshed before they expire...
B snippet: Access tokens must be renewed prior to expiry...
----------------------------------------------------------------------------------------------------
A score of 1.0 means identical content; 0.82 (default threshold) catches near-duplicates while filtering loosely related content.
Exit behaviour
Exits 0 whether or not duplicates are found. Use --format json and inspect result_count in CI pipelines.
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 · 62 lines · 0 tokens per session scan A 24110ade3194
check 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 449 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.
check compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| checkhiromaily/docs-ssot | Command | 2 | 7mo ago | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 149k | 2d ago | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 149k | 2d ago | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 149k | 2d ago | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 149k | 2d ago | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 149k | 2d ago | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 149k | 2d ago | MIT | A | 14 | Claude Code |