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 agentmods add skills/intent-integrity-chain/kit/iikit-01-specifynpx skills add intent-integrity-chain/kit --skill iikit-01-specifygit clone --depth 1 https://github.com/intent-integrity-chain/kitWrote 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/intent-integrity-chain/kit/iikit-01-specify)<a href="https://agentmods.dev/skills/intent-integrity-chain/kit/iikit-01-specify"><img src="https://agentmods.dev/badge/skills/intent-integrity-chain/kit/iikit-01-specify.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00071 | $0.01426 |
| Opus 5 | $0.00036 | $0.00713 |
| Sonnet 5 | $0.00014 | $0.00285 |
| Haiku 4.5 | $0.00007 | $0.00143 |
Grade A, and why
iikit-01-specify 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 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.
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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intent Integrity Kit Specify
Process steps in order. Do not skip ahead.
Create or update a feature specification from a natural language description.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Constitution Loading
Load constitution per constitution-loading.md (soft mode — warn if missing, proceed without).
The text after /iikit-01-specify is the feature description.
Step 1 — Bug-Fix Intent Detection
Analyze the description using contextual analysis (not keyword-only) to determine primary intent: fix existing broken behavior vs. add new capability.
- Bug-fix signals: "fix", "crash", "broken", "bug", "doesn't work", "fails", "error" — when describing broken existing behavior.
- Not bug-fix: "Add error handling", "Implement crash recovery" — these describe new capabilities, not fixes.
If bug-fix intent is detected:
- Display: "This sounds like a bug fix. Consider using
/iikit-bugfixinstead." - Show example:
/iikit-bugfix '<the user description>' - Ask the user to confirm: proceed with specification (genuinely a new feature) or switch to
/iikit-bugfix - User confirms new feature → proceed to Step 2; user wants bugfix → stop.
If bug-fix intent was NOT detected, or the user confirmed this is a new feature, proceed immediately to Step 2. If the user switched to /iikit-bugfix, finish here.
Step 2 — Generate Branch Name
Create 2-4 word action-noun name from description:
- "I want to add user authentication" -> "user-auth"
- "Implement OAuth2 integration for the API" -> "oauth2-api-integration"
Proceed immediately to Step 3.
Step 3 — Create Feature Branch and Directory
Check current branch. If on main/master/develop, suggest creating feature branch (default). If already on feature branch, suggest skipping.
Unix/macOS/Linux:
bash .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/create-new-feature.sh --json "$ARGUMENTS" --short-name "your-short-name"
# Add --skip-branch if user declined branch creation
Windows (PowerShell):
pwsh .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/powershell/create-new-feature.ps1 -Json "$ARGUMENTS" -ShortName "your-short-name"
# Add -SkipBranch if user declined
What ships with it
28 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.
- references/constitution-loading.md 1.5 KB
- references/formatting-guide.md 3.9 KB
- references/model-recommendations.md 2.5 KB
- references/phase-separation-rules.md 1.6 KB
- scripts/bash/common.sh 25 KB runs code
- scripts/bash/create-new-feature.sh 10 KB runs code
- scripts/bash/generate-dashboard-safe.sh 1.8 KB runs code
- scripts/bash/next-step.sh 14 KB runs code
- scripts/dashboard/package.json 20 B
- scripts/dashboard/public/index.html 206 KB
- scripts/dashboard/src/analyze.js 7.0 KB runs code
- scripts/dashboard/src/board.js 3.2 KB runs code
- scripts/dashboard/src/bugs.js 4.9 KB runs code
- scripts/dashboard/src/checklist.js 2.1 KB runs code
- scripts/dashboard/src/generate-dashboard.js 10 KB runs code
- scripts/dashboard/src/integrity.js 1.7 KB runs code
- scripts/dashboard/src/parser.js 44 KB runs code
- scripts/dashboard/src/pipeline.js 5.9 KB runs code
- scripts/dashboard/src/planview.js 9.4 KB runs code
- scripts/dashboard/src/public/index.html 205 KB
- scripts/dashboard/src/storymap.js 1.4 KB runs code
- scripts/dashboard/src/testify.js 6.2 KB runs code
- scripts/dashboard/template.js 213 KB runs code
- scripts/powershell/common.ps1 14 KB runs code
- scripts/powershell/create-new-feature.ps1 10 KB runs code
- scripts/powershell/generate-dashboard-safe.ps1 1.8 KB runs code
- scripts/powershell/next-step.ps1 11 KB runs code
- templates/spec-template.md 3.9 KB
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 First seen · 154 lines · 71 tokens per session scan A 7150b0837973
iikit-01-specify is a skill published in the GitHub repository intent-integrity-chain/kit (47 stars, last pushed 3mo ago), licensed MIT. It adds 71 tokens to every session and 1,426 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…