Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/TserenTserenov/FMT-exocortex-templatenpx agentmods add skills/tserentserenov/fmt-exocortex-template/iwe-updateWrote 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/iwe-update)<a href="https://agentmods.dev/skills/tserentserenov/fmt-exocortex-template/iwe-update"><img src="https://agentmods.dev/badge/skills/tserentserenov/fmt-exocortex-template/iwe-update/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/iwe-update"><img src="https://agentmods.dev/badge/skills/tserentserenov/fmt-exocortex-template/iwe-update.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.01461 |
| Opus 5 | $0.00015 | $0.00731 |
| Sonnet 5 | $0.00006 | $0.00292 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
iwe-update scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL "https://raw.githubusercontent.com/TserenTserenov/FMT-exocortex-template/main/CHANGELOG.md" How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IWE Update (агент-обновитель)
Роль: R6 Кодировщик. Один выход: обновлённый IWE + объяснение что изменилось. Триггер: «обнови IWE», «обновись»,
/iwe-update, или агент предлагает после обнаружения новой версии.
Алгоритм
0. Extensions before
bash .claude/scripts/load-extensions.sh iwe-update before
Код 0 → прочитать каждый путь из вывода в алфавитном порядке и выполнить
инструкции до превью. Код 1 → расширений нет, продолжить. Любой другой код или
ошибка обязательного шага расширения → обновление не начинать, показать
настоящую причину ошибки.
1. Превью (--check)
Запустить update.sh в режиме превью:
cd "$IWE_TEMPLATE" && bash update.sh --check 2>&1
Из вывода извлечь:
- Версию upstream (текущая vs новая)
- Список новых файлов
- Список обновлённых файлов
- Количество строк изменений
Если «Всё актуально» → сообщить пользователю и завершить.
2. CHANGELOG — что изменилось
CHANGELOG.md больше не доставляется локально (WP-401 Ф6.1) — читать по raw-URL:
curl -fsSL "https://raw.githubusercontent.com/TserenTserenov/FMT-exocortex-template/main/CHANGELOG.md"
Найти записи между текущей и новой версией.
Объяснить пользователю на человеческом языке:
- Что добавлено и зачем (не список файлов, а польза)
- Что изменилось в поведении (может ли сломать что-то)
- Что исправлено (баги, которые могли затрагивать пользователя)
Формат объяснения:
## Обновление IWE: v{old} → v{new}
**Что нового:**
- [1-3 пункта на языке пользователя, не разработчика]
**Что изменилось:**
- [поведение, которое может заметить пользователь]
**Исправления:**
- [если есть]
3. Анализ совместимости
Перед применением — проверить пользовательские кастомизации:
3a. Extensions:
ls extensions/*.md 2>/dev/null
Если есть extension-файлы → проверить, не конфликтуют ли новые extension points с существующими файлами.
3b. params.yaml:
Прочитать params.yaml. Если обновление добавляет новые параметры → сообщить пользователю:
«Появился новый параметр
X(default: Y). Хотите изменить?»
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.
- 5d ago Changed · +1 lines add0e5142c38
- 10d ago First seen · 171 lines · 31 tokens per session scan A c953a13625ab
iwe-update is a skill published in the GitHub repository TserenTserenov/FMT-exocortex-template (51 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 1,461 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.