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 skills add AlexZio00/sovereign-skills --skill ssot-auditgit clone --depth 1 https://github.com/AlexZio00/sovereign-skillsWrote 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/skills/alexzio00/sovereign-skills/ssot-audit)<a href="https://agentmods.dev/skills/alexzio00/sovereign-skills/ssot-audit"><img src="https://agentmods.dev/badge/skills/alexzio00/sovereign-skills/ssot-audit/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/skills/alexzio00/sovereign-skills/ssot-audit"><img src="https://agentmods.dev/badge/skills/alexzio00/sovereign-skills/ssot-audit.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.00039 | $0.02283 |
| Opus 5.5 | $0.00016 | $0.00913 |
| Sonnet 5.5 | $0.00008 | $0.00457 |
| Haiku 4.5 | $0.00004 | $0.00228 |
Grade A, and why
ssot-audit 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 yesterday.
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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SSOT Audit: find the source of truth, then consolidate
Purpose
One fact often lives in several artifacts (docs, code, config, tickets, notes) and the copies drift or contradict each other. This skill finds where the fact lives and how many copies exist, names one source of truth (Phase A, read-only), and after user approval brings the other copies in line with it (Phase B).
doc-drift covers only the files Claude Code loads into context (CLAUDE.md, rules, memory, skills, agents). This skill works on any artifact in a repo or notes folder.
Dominant variable: is the chosen source of truth really the most authoritative location and the one updated most often? A wrong pick makes consolidation distort the fact instead of fixing it.
Discard if: the fact already lives in exactly one place (no duplication), or the scope is only CLAUDE.md / rules / memory (use doc-drift).
Verify before acting: every artifact found in Phase A is a snapshot from the time of the audit. Before Phase B edits anything, re-check the current state with Glob/Grep. "I saw it during the audit, so it must still be right" is not allowed.
Trigger
- "where is this fact scattered", "what is the source of truth", "consolidate the duplicated content"
- "find where this fact is duplicated", "consolidate the source of truth"
/ssot-audit
Workflow
Phase A: audit (read-only by policy, not by enforcement)
Edit is listed in tools: (the tool list is descriptive metadata, nothing enforces it), so keeping this phase read-only is a rule you follow.
- Fix the scope (repo, folder or notes directory) and the tracked item: one specific value, spec or decision, not a whole document.
- Enumerate every occurrence of the item with the Grep and Glob tools (no shell flags needed). Narrow Grep with its
globortypefilter to text files, and exclude__pycache__and build output (for example glob!**/__pycache__/**), otherwise compiled-file matches have to be filtered by hand. - Classify each occurrence: exact copy, paraphrase, partial excerpt, stale, or contradictory.
- stale: the copy differs from the source of truth and you can show it is an earlier version of the fact (version history, a changelog, or the source of truth explicitly superseding it). Action: reference or dedupe, after Phase B approval.
- contradictory: the copy differs and you cannot show it is the older one. Action: reconcile.
- Pick a source-of-truth candidate: the most authoritative location, closest to the point where the fact actually changes (code or config for a value, a spec document for a decision, a state file for a status). Designate it with a one-line reason; never pick arbitrarily.
- Two or more candidates of the same kind (for example constants in two different modules): do not choose, classify as reconcile.
- One source of truth but a non-canonical copy holds a different value: that copy is also reconcile. An older date alone does not make it stale.
- For each non-canonical occurrence choose an action:
- dedupe: remove the copy (removing content inside a file is done with Edit in Phase B; deleting a whole file is only proposed to the user, who runs the command, for example
git rm <file>; this skill has no tool to delete files) - reference: replace the copy with a link or pointer to the source of truth
- reconcile: contradiction, a human has to decide
- dedupe: remove the copy (removing content inside a file is done with Edit in Phase B; deleting a whole file is only proposed to the user, who runs the command, for example
- Output the audit report: occurrence table (location, kind, action), source-of-truth proposal with reason, and a separate list of contradictions.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 133 lines · 39 tokens per session scan A 248ed69c3df1
ssot-audit is a skill published in the GitHub repository AlexZio00/sovereign-skills (146 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 2,283 once invoked, about $0.0002 per session on Opus 5.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-10-22.
Other skills, from other repositories
nobrainer-dispatcher
Use when the owner says nb-dispatcher or nobrainer-dispatcher, or when an approved plan has multiple queued work units that require ready-set selection, dependency-aware ordering, bounded parallel batches, retry scheduling, or routing audited results to the next queued unit; do not use for one coherent task, one…
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
feedback-page-generator
Deprecated compatibility entry for Feedback Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Feedback Page.
status-page-generator
Deprecated compatibility entry for Status Page construction. This page is now maintained in Pagina; install and use page-builder to build a new Status Page.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.