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 iwe-bug-reportgit 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/iwe-bug-report)<a href="https://agentmods.dev/skills/tserentserenov/fmt-exocortex-template/iwe-bug-report"><img src="https://agentmods.dev/badge/skills/tserentserenov/fmt-exocortex-template/iwe-bug-report/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-bug-report"><img src="https://agentmods.dev/badge/skills/tserentserenov/fmt-exocortex-template/iwe-bug-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.01221 |
| Opus 5 | $0.00016 | $0.00611 |
| Sonnet 5 | $0.00007 | $0.00244 |
| Haiku 4.5 | $0.00003 | $0.00122 |
Grade A, and why
iwe-bug-report 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 6d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Отчёт об ошибке платформы IWE
Проблема: $ARGUMENTS
When to use
Сообщить об ошибке или проблеме платформы IWE. Создаёт GitHub issue в FMT-exocortex-template.
Algorithm
Шаг 0. Проверка на запрос справки (issue #274)
Если $ARGUMENTS пуст, отсутствует, или равен --help/-h/help — НЕ создавать issue. Вместо этого вывести:
«
/iwe-bug-report [описание проблемы]— сообщает об ошибке платформы IWE, создаёт GitHub issue в FMT-exocortex-template. Опиши, что произошло и что ожидалось, например:/iwe-bug-report day-close не архивирует DayPlan.»
Прекратить выполнение.
Шаг 1. Категоризация
Определи категорию по содержанию $ARGUMENTS:
| Метка | Когда |
|---|---|
bug |
Скилл / протокол / скрипт работает не так, как задумано |
documentation |
Неточность или пробел в документации / memory / SKILL.md |
enhancement |
Улучшение существующего поведения (не новый функционал) |
question |
Поведение непонятно, нужно уточнение |
Шаг 2. Сбор деталей
Извлеки из $ARGUMENTS и контекста сессии:
- Что произошло: конкретное наблюдаемое поведение
- Что ожидалось: правильное поведение по протоколу
- Шаги воспроизведения: команда / скилл / триггер (если применимо)
- Где: путь к скиллу / протоколу / скрипту или имя файла
Если какой-либо элемент не указан — пропусти соответствующий блок в issue (не оставляй пустые заголовки).
Шаг 3. Получить версию IWE
Запусти:
git -C "$HOME/IWE/FMT-exocortex-template" log -1 --format="%h %ad" --date=short 2>/dev/null || echo "неизвестно"
Шаг 4. Проверить gh CLI
Запусти:
gh auth status 2>&1 | head -3
Если gh не авторизован или не установлен — выведи сообщение:
«
ghCLI не найден или не авторизован. Установи (macOS:brew install gh; Linux:apt install ghили https://cli.github.com/), затемgh auth login. Issue не создан.» Прекрати выполнение.
Шаг 5. Создать issue
Собери переменные:
TITLE: до 80 символов, формат[ТИП] Краткое описаниеCATEGORY: метка из шага 1DATE: сегодняшняя дата (YYYY-MM-DD)IWE_VERSION: из шага 3
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.
- 6d ago Changed · +1 lines 9ac44b9799e5
- 11d ago First seen · 135 lines · 33 tokens per session scan A 627aa06118e3
iwe-bug-report is a skill published in the GitHub repository TserenTserenov/FMT-exocortex-template (51 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 1,221 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…
debugging-pipelines
Use when a data pipeline, model, or analysis produces unexpected results, errors, or performance degradation. Enforces root cause investigation before any fix.
ap-depth-prober
Report the compatibility redirect to ap-worker; this retired role cannot perform new work.
openlore-debug
Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.
ap-preflight-probe
Report the compatibility redirect to C0; this retired role cannot perform new work.
openlore-analyze-codebase
Run a full static OpenLore analysis and summarize architecture, call graph, refactoring issues, and duplicate code. Use when asked to analyze, map, or assess a codebase without LLM inference.