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 skills/tserentserenov/fmt-exocortex-template/audit-installationnpx skills add TserenTserenov/FMT-exocortex-template --skill audit-installationgit clone --depth 1 https://github.com/TserenTserenov/FMT-exocortex-templateWhat 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 | $0.00131 | $0.03502 |
| Opus 5 | $0.00066 | $0.01751 |
| Sonnet 5 | $0.00026 | $0.00700 |
| Haiku 4.5 | $0.00013 | $0.00350 |
Grade A, and why
audit-installation 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 today.
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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Аудит инсталляции IWE
Service Clause: VR.SC.005-installation-audit Роль: VR.R.002 Аудитор (PACK-verification) — субагент с context isolation Принцип: детектор отчитывается, оператор делает (см.
scripts/iwe-drift.sh:7-11). Auto-fix не входит в обещание.
Аргументы: $ARGUMENTS
When to use
Аудит пользовательской инсталляции IWE. Запускает scripts/iwe-audit.sh + MCP healthcheck + smoke-test ритуала через sentinel-механику (контракт dry-run-contract.md), передаёт отчёт subagent'у в роли VR.R.002 Аудитор (context isolation) → verdict ✅/⚠️/❌ по 6 компонентам (Inventory, L1 drift, DS-strategy, L3 customizations, MCP, ритуал). Используй после restore из бэкапа, после update.sh, или при еженедельной сверке.
Обещание
За ≤5 минут — markdown-отчёт ✅/⚠️/❌ по 6 компонентам инсталляции:
- Inventory — все ли критичные L1-файлы (CLAUDE.md, скиллы, протоколы) на месте
- L1 drift — расхождения с FMT-exocortex-template
- DS-strategy — git status + diff с FMT-strategy-template
- L3 customizations — extensions/, отличия params.yaml от skeleton, AUTHOR-ONLY зоны
- MCP healthcheck — 4 tools отвечают (с уважением к подписочному гейтингу DP.SC.112)
- Ритуал smoke-test —
/run-protocol close dayзапускается под sentinel-защитой, доходит до write-шагов (см.memory/dry-run-contract.md)
Verdict выносит subagent в роли Аудитора, читая отчёт без знаний о текущей сессии (context isolation).
Шаг 1. Детерминированные проверки (bash)
Найти и запустить iwe-audit.sh через fallback-цепочку (author-mode → workspace, user-mode → $IWE_SCRIPTS из ~/.iwe-paths):
if [ -n "${IWE_SCRIPTS:-}" ] && [ -f "$IWE_SCRIPTS/iwe-audit.sh" ]; then
# $IWE_SCRIPTS first (#566): the hardcoded workspace copy, when it exists at
# all, is a stale leftover — the installer points IWE_SCRIPTS at the template.
AUDIT_SCRIPT="$IWE_SCRIPTS/iwe-audit.sh"
elif [ -f "$HOME/IWE/scripts/iwe-audit.sh" ]; then
AUDIT_SCRIPT="$HOME/IWE/scripts/iwe-audit.sh"
else
echo "iwe-audit.sh не найден. Если \$IWE_SCRIPTS не выставлен — выполни 'source \$HOME/.iwe-paths' (или перезапусти shell), затем повтори. Если файла .iwe-paths нет — запусти setup.sh из FMT-шаблона."
exit 1
fi
bash "$AUDIT_SCRIPT" $([ "${ARGUMENTS:-}" = "--critical" ] && echo "--critical")
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.
- today Changed · -13 lines 2ab7fc246cdd
- yesterday First seen · 255 lines · 131 tokens per session scan A 931d80593488
audit-installation is a skill published in the GitHub repository TserenTserenov/FMT-exocortex-template (48 stars, last pushed today), licensed MIT. It adds 131 tokens to every session and 3,502 once invoked, about $0.0007 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
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.
agent-management
Create, manage, and orchestrate AI agents using the AI Maestro CLI. Use when the user asks to "create agent", "list agents", "delete agent", "hibernate agent", "wake agent", "install plugin", "show agent", "restart agent", or any agent lifecycle management task.
iterative-retrieval
Pattern for progressively refining context retrieval to solve the subagent context problem. Use when spawning subagents that need codebase context they cannot predict upfront, or when building multi-agent workflows where context is progressively refined.
Skill Creator
Create new Cursor Skills following the standard directory structure.
ccc-orchestrate
Cross-runtime Orchestrator/Executor — Fable/Opus writes a goal file, GPT-5.6 Sol (codex) or a Sonnet subagent executes it, Fable/Opus verifies against acceptance criteria before reporting done.
data
Set up database / persistent-state discipline for a project with a DB. Authors a data-auditor agent (5 categories of integrity check), a migration-create skill, query-discipline rule (CLI > MCP DB tool for reads), and edit-time regen hook — all derived from the project's actual schema, migration framework, and…