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/skill-creatorWrote 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/skill-creator)<a href="https://agentmods.dev/skills/tserentserenov/fmt-exocortex-template/skill-creator"><img src="https://agentmods.dev/badge/skills/tserentserenov/fmt-exocortex-template/skill-creator/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/skill-creator"><img src="https://agentmods.dev/badge/skills/tserentserenov/fmt-exocortex-template/skill-creator.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.00093 | $0.02473 |
| Opus 5 | $0.00046 | $0.01236 |
| Sonnet 5 | $0.00019 | $0.00495 |
| Haiku 4.5 | $0.00009 | $0.00247 |
Grade A, and why
skill-creator 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/skill-creator — create an IWE skill
Scope: create a new skill OR guide an update to an existing skill in
.claude/skills/or.kimi/skills/. Not in scope: full re-scaffold without deleting the oldSKILL.mdfirst (delete manually, then call/skill-creatoragain); creating a WP; creating a Pack. Role: ad-hoc content-role «Инженер скиллов»; formalize in Pack if ≥3 skills/year.
When to use
- Pilot wants a new skill for a repeated workflow.
- A new tool/agent/system needs a Service Clause + Role + SKILL.md.
- A skill needs promotion from author repo to
FMT-exocortex-template.
Preconditions (checked, not performed)
- WP Gate precondition. The task must be attached to an agreed WP in the weekly plan or explicitly named by the pilot.
/skill-creatordoes not conduct the WP Gate ritual itself. - Routing Gate. Decide target platform (Claude vs Kimi) and level (project vs user). Default: project-level
.claude/skills/in the author repo. - IntegrationGate hard-check.
DP.SC.*andDP.ROLE.*must exist in the PACK repo. If not, the skill stops and offers to create them. Bypass only by explicit pilot instruction «пропусти gate» — no code flag.
Algorithm
Step 1 — Check WP Gate precondition
Look up the current weekly plan (current/WeekPlan W{N}.md) or ask:
К какому РП привязано создание скилла?
If no WP is named and none matches the skill topic → stop:
Создание скилла требует согласованного РП. Сначала откройте РП через WP Gate.
Step 2 — Routing Gate
Ask or infer:
| Question | Default |
|---|---|
| Claude или Kimi? | Claude |
| project-level или user-level? | project-level |
| governance-репо для учёта? | ${IWE_GOVERNANCE_REPO:-DS-strategy} |
Target path:
- Claude project:
.claude/skills/<name>/ - Kimi project:
.kimi/skills/<name>/ - User level:
~/.claude/skills/<name>/or~/.kimi/skills/<name>/
Step 2.5 — Detect existing skill
Check whether <target_path>/SKILL.md already exists.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 79d832e4e723
- 9d ago First seen · 232 lines · 93 tokens per session scan A c492e3b80ee2
skill-creator is a skill published in the GitHub repository TserenTserenov/FMT-exocortex-template (50 stars, last pushed today), licensed MIT. It adds 93 tokens to every session and 2,473 once invoked, about $0.0005 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.