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 integration-gategit 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/integration-gate)<a href="https://agentmods.dev/skills/tserentserenov/fmt-exocortex-template/integration-gate"><img src="https://agentmods.dev/badge/skills/tserentserenov/fmt-exocortex-template/integration-gate/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/integration-gate"><img src="https://agentmods.dev/badge/skills/tserentserenov/fmt-exocortex-template/integration-gate.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.00056 | $0.00658 |
| Opus 5.5 | $0.00022 | $0.00263 |
| Sonnet 5.5 | $0.00011 | $0.00132 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
integration-gate 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 10d 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.
What it actually says
/integration-gate — IntegrationGate
Триггер: новый инструмент / агент / детектор / система / метод
Приоритет: БЛОКИРУЮЩЕЕ — пропуск фазы = паттерн P10 (DP.FM.010)
Чеклист (4 шага — строго по порядку)
Пропуск фазы → зафиксировать как инцидент:
C2.3.Operations/Incidents/своего ecosystem-development репозитория (если есть) илиincidents/governance-репо
-
Обещание (Service Clause). Какое обещание инструмент даёт потребителю?
Создать/обновитьDP.SC.NNNвPACK-digital-platform/.../08-service-clauses/.
Содержит: триггер · входы · выходы · время отклика · инвариант · режим отказа. -
Сценарии использования. Кто запускает? Когда? Зачем? В каком контексте? Что делает с результатом?
Минимум 3 сценария с разными потребителями. Приложить к Service Clause. -
Роль. Какую роль в системе играет инструмент?
Создать/обновитьDP.ROLE.NNNвPACK-digital-platform/.../02-domain-entities/.
Содержит: обязанности · полномочия · связи · входы/выходы как артефакты.
Идентифицировать Kind (род) и Owner Role (кто владеет в надсистеме). Шаблон: DP.D.033. -
Реализация. Только после (1)–(3).
Код · тесты · регистрация в hooks/config · smoke-test.
Заголовок реализации:# see DP.SC.NNN, DP.ROLE.NNN
Исключения (IntegrationGate НЕ нужен)
- Правка существующего инструмента без изменения его обещания.
- Bugfix без изменения поведения снаружи.
- Рефакторинг (переименование, реорганизация) без функциональных изменений.
- Экспериментальный скрипт на один запуск (если запускается повторно — уже инструмент).
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.
- 10d ago Changed 565e669196bf
- 1mo ago Changed · +1 lines 8100e7475c7f
- 1mo ago First seen · 54 lines · 56 tokens per session scan A 0d2a6d2a7b2e
integration-gate is a skill published in the GitHub repository TserenTserenov/FMT-exocortex-template (63 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 658 once invoked, about $0.0002 per session on Opus 5.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.