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 TserenTserenov/FMT-exocortex-template --skill audit-docsgit clone --depth 1 https://github.com/TserenTserenov/FMT-exocortex-templateWrote 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/tserentserenov/fmt-exocortex-template/audit-docs)<a href="https://agentmods.dev/skills/tserentserenov/fmt-exocortex-template/audit-docs"><img src="https://agentmods.dev/badge/skills/tserentserenov/fmt-exocortex-template/audit-docs/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/tserentserenov/fmt-exocortex-template/audit-docs"><img src="https://agentmods.dev/badge/skills/tserentserenov/fmt-exocortex-template/audit-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
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.00028 | $0.02236 |
| Opus 5 | $0.00014 | $0.01118 |
| Sonnet 5 | $0.00006 | $0.00447 |
| Haiku 4.5 | $0.00003 | $0.00224 |
Grade A, and why
audit-docs 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 3d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Docs (R24 Аудитор)
Роль: R24 Аудитор. Полное описание:
PACK-digital-platform/pack/digital-platform/02-domain-entities/DP.ROLE.024-auditor.md(WP-224). Маппинг: R24 = VR.R.002. Метод: R24 coverage по категориям + R23 pair-diff между парамикод файл ↔ docs файл. Получатель отчёта: владелец репо в другой временной позиции (категория 3 — внешняя проектная роль). Это аудит в строгом смысле — не автор кода, не ты сейчас. Тип роли (DP.D.080): R24 — контрольная роль. Read-only к аудитуемым артефактам. Отчёт = output-канал, не изменение аудитуемого.
Аргументы: $ARGUMENTS
Что делает
Проходит указанный репо и формирует отчёт о расхождениях между кодом и документацией. Не правит ни код, ни docs — только отчёт.
Параметр
--repo <path>(обязателен) или.(текущая директория).--init --repo <path>— направляемая подготовка конфигурации; аудит не запускает.
Владение конфигурацией
| Ответственность | Подотчётная роль |
|---|---|
| Решить, что покрытие документацией требуется, и утвердить модель репозитория | Владелец репозитория |
| Определить категории документации и пары «источник ↔ документация» | R5 Архитектор совместно с владельцем |
| Материализовать утверждённый YAML | Мейнтейнер или агент-исполнитель |
| Потреблять YAML и сообщать о расхождениях | R24 Аудитор / audit-docs |
| Поставить шаблон, схему, bootstrap и утверждение о владении | Мейнтейнер платформы / FMT |
Блокирующее ограничение: агент вправе создать docs/.audit-context.yaml
только после того, как владелец утвердил категории и маппинги. R24 Аудитор не
изобретает семантическую модель ни во время аудита, ни перед ним.
Bootstrap (--init)
- Прочитать
<repo>/CLAUDE.md; определить владельца и R5 Архитектора. - Показать им пример
.claude/skills/audit-docs/.audit-context.yaml.example. - Получить от владельца явное утверждение списка категорий и каждой пары
source_patterns↔docs_patterns/file_naming. Без утверждения остановиться. - Материализовать утверждённую модель в
<repo>/docs/.audit-context.yaml, поставитьowner_approved: true,approved_byи реальную дату. - Выполнить валидацию ниже. Только успешный файл становится входом аудита.
What ships with it
1 file 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.
- 3d ago Changed · +1 lines f267893c84ac
- 9d ago First seen · 174 lines · 28 tokens per session scan A 1b1d7bb57038
audit-docs is a skill published in the GitHub repository TserenTserenov/FMT-exocortex-template (49 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 2,236 once invoked, about $0.0001 per session on Opus 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-08-30.
Other skills, from other repositories
team-management-debugging
Systematic debugging — a four-phase root-cause methodology, boundary instrumentation for multi-component systems, the 3-fix escalation rule, and a verification gate to run before claiming anything is fixed. Use on any test failure, production bug, build failure, performance regression, or integration glitch, and…
team-management-receiving-feedback
How to receive code review as technical evaluation rather than social performance — verify claims against the codebase before implementing, push back with evidence, and drop the performative agreement. Use when responding to a human reviewer, a PR comment, or another AI reviewer, and when deciding whether a suggestion…
team-management-tdd-discipline
Test-driven development discipline — when TDD applies, when forcing it is wrong, and the RED-GREEN-REFACTOR loop with an explicit "watch it fail" step. Use when writing or reviewing tests, fixing a bug, changing behaviour, or deciding whether a change needs a test at all. Triggers on bug fixes, new validation or…
data-profiling
Use BEFORE dispatching any subagent that needs to understand the dataset. Generates a high-density, PII-free data profile in Markdown so subagents receive structured context instead of raw data.
leakage-guard
Use whenever building features for time-series or any temporal dataset. Enforces strict temporal integrity: no future data in features, no post-event information, correct CV strategy.
verification-before-delivery
Use when any analysis, model, or report is claimed to be complete. Runs mandatory artifact integrity, statistical evidence, and reproducibility checks before any delivery.