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 extendgit 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/extend)<a href="https://agentmods.dev/skills/tserentserenov/fmt-exocortex-template/extend"><img src="https://agentmods.dev/badge/skills/tserentserenov/fmt-exocortex-template/extend/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/extend"><img src="https://agentmods.dev/badge/skills/tserentserenov/fmt-exocortex-template/extend.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.00031 | $0.02113 |
| Opus 5 | $0.00015 | $0.01056 |
| Sonnet 5 | $0.00006 | $0.00423 |
| Haiku 4.5 | $0.00003 | $0.00211 |
Grade A, and why
extend 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 4d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/extend — Каталог расширяемости IWE
Триггер:
/extend, «что я могу расширить?», «как настроить протокол», «как добавить свой шаг». Роль: R6 Кодировщик. Один выход: карта того, что доступно + конкретные инструкции.
Алгоритм
1. Определить область запроса
Если аргумент указан (например /extend day-open) → показать только этот протокол.
Если аргумент пустой → показать полный каталог.
2. Показать текущее состояние кастомизаций
ls {{WORKSPACE_DIR}}/extensions/*.md 2>/dev/null || echo "(нет расширений)"
cat {{WORKSPACE_DIR}}/params.yaml 2>/dev/null
Сообщить:
- Какие расширения уже установлены (✅)
- Какие параметры уже изменены от defaults
3. Вывести каталог
Extension points (файлы в extensions/)
| Протокол | Hook | Файл для создания | Когда выполняется |
|---|---|---|---|
protocol-close |
checks |
extensions/protocol-close.checks.md |
ДО commit+push — pre-commit gate (R4.3, WP-273) |
protocol-close |
after |
extensions/protocol-close.after.md |
После чеклиста, перед верификацией |
day-open |
before |
extensions/day-open.before.md |
Перед шагом 1 — утренние ритуалы |
day-open |
after |
extensions/day-open.after.md |
После «Требует внимания», перед DayPlan |
day-close |
checks |
extensions/day-close.checks.md |
После governance batch, перед архивацией |
day-close |
after |
extensions/day-close.after.md |
После итогов дня, перед верификацией |
week-close |
before |
extensions/week-close.before.md |
Перед ротацией уроков |
week-close |
after |
extensions/week-close.after.md |
После аудита memory |
protocol-open |
after |
extensions/protocol-open.after.md |
После ритуала согласования |
protocol-open |
sync |
extensions/protocol-open.sync.md |
Переопределяет поведение синхронизации на шаге 3b |
day-open |
checks |
extensions/day-open.checks.md |
Перед commit, после подготовки DayPlan |
day-close |
before |
extensions/day-close.before.md |
Перед первыми шагами закрытия дня |
month-close |
before |
extensions/month-close.before.md |
Перед первыми шагами закрытия месяца |
month-close |
after |
extensions/month-close.after.md |
После итогов месяца, перед верификацией |
strategy-session |
before |
extensions/strategy-session.before.md |
Перед началом стратегической сессии |
strategy-session |
after |
extensions/strategy-session.after.md |
После итогов стратегической сессии |
iwe-update |
before |
extensions/iwe-update.before.md |
До превью и применения обновления |
iwe-update |
checks |
extensions/iwe-update.checks.md |
После применения, до успешного итогового отчёта |
iwe-update |
after |
extensions/iwe-update.after.md |
После итогового отчёта об обновлении |
verify |
before |
extensions/verify.before.md |
До выбора типа и запуска проверки |
verify |
checks |
extensions/verify.checks.md |
После основной проверки, до итогового verdict |
verify |
after |
extensions/verify.after.md |
После показа итогового verdict |
archgate |
before |
extensions/archgate.before.md |
До принципов и начала архитектурной оценки; блокирует старт при ошибке |
archgate |
checks |
extensions/archgate.checks.md |
После DRR, до единственной публикации вердикта; блокирует публикацию при ошибке |
archgate |
after |
extensions/archgate.after.md |
После публикации; предупреждает об ошибках и никогда не меняет вердикт |
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.
- 4d ago Changed · +1 lines 44f503db81a2
- 9d ago First seen · 157 lines · 31 tokens per session scan A 36405c8038f4
extend is a skill published in the GitHub repository TserenTserenov/FMT-exocortex-template (49 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 2,113 once invoked, about $0.0002 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.