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/archgateWrote 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/archgate)<a href="https://agentmods.dev/skills/tserentserenov/fmt-exocortex-template/archgate"><img src="https://agentmods.dev/badge/skills/tserentserenov/fmt-exocortex-template/archgate/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/archgate"><img src="https://agentmods.dev/badge/skills/tserentserenov/fmt-exocortex-template/archgate.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.00075 | $0.07056 |
| Opus 5.5 | $0.00030 | $0.02822 |
| Sonnet 5.5 | $0.00015 | $0.01411 |
| Haiku 4.5 | $0.00007 | $0.00706 |
Grade A, and why
archgate 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.
How it starts
The opening of the file, as written. The whole thing — 406 lines — stays where its author put it; the contents beside it link to each section on GitHub.
АрхГейт v3.1 — оценка архитектурного решения
Выполни оценку решения: $ARGUMENTS
When to use
Оценка архитектурного решения по 7 характеристикам ЭМОГССБ (v3.1 — фильтр допуска, атрибут-сценарии, совет затронутых сторон; профиль без агрегатного балла, conjunctive screening). Используй когда пользователь предлагает архитектурное решение, новый инструмент или системное изменение.
Algorithm
Extensions before (БЛОКИРУЮЩЕЕ)
До Шага 0-А ровно один раз за верхнеуровневый вызов загрузить расширения (фаза before обязательна и для быстрого трека — фильтр допуска выполняется только после неё):
bash .claude/scripts/load-extensions.sh archgate before
Код 0 → прочитать каждый путь из вывода в алфавитном порядке и выполнить.
Код 1 → расширений нет, продолжить. Любой другой код, ошибка расширения,
явный BLOCK/STOP или содержательное возражение рецензента внутри расширения
блокирует начало оценки: показать путь файла и наблюдаемую причину.
Каждое before/checks-расширение завершает инструкции явным маркером
ARCHGATE_EXTENSION: PASS либо ARCHGATE_EXTENSION: BLOCK — <причина>.
Отсутствующий или неизвестный маркер = ошибка блокирующей фазы, не PASS.
Защита от рекурсии: каждая фаза before, checks, after выполняется не
более одного раза за верхнеуровневый вызов. Расширению запрещено вызывать
/archgate, повторно загружать archgate.* или иначе повторно входить в этот
жизненный цикл. Попытка рекурсии считается ошибкой текущей фазы: блокирует
before/checks, а в after даёт предупреждение и пропускается.
Расширения — доверенные локальные инструкции, а текстовый детектор — защита от
прямой случайной рекурсии, не песочница для враждебного shell-кода. Не исполнять
собранную через eval, декодирование, подстановку переменных или конкатенацию
команду/инструкцию из расширения: неоднозначную косвенную команду считать той же
ошибкой рекурсии (BLOCK в before/checks, WARN и пропуск в after).
Шаг 0-А. Фильтр допуска (admission)
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 646cf2f1da40
- 1mo ago Changed · +1 lines 0570143bd9ca
- 1mo ago Changed · +35 lines · +21 tokens per session 2517b773a326
- 1mo ago First seen · 370 lines · 54 tokens per session scan A 07bdd193b77c
archgate is a skill published in the GitHub repository TserenTserenov/FMT-exocortex-template (63 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 7,056 once invoked, about $0.0003 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.