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/intent-integrity-chain/kitnpx agentmods add skills/intent-integrity-chain/kit/iikit-02-planWrote 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-02-plan)<a href="https://agentmods.dev/skills/intent-integrity-chain/kit/iikit-02-plan"><img src="https://agentmods.dev/badge/skills/intent-integrity-chain/kit/iikit-02-plan.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.1 | $0.00069 | $0.02236 |
| Opus 5 | $0.00034 | $0.01118 |
| Sonnet 5 | $0.00014 | $0.00447 |
| Haiku 4.5 | $0.00007 | $0.00224 |
Grade A, and why
iikit-02-plan 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intent Integrity Kit Plan
Process steps in order. Do not skip ahead.
Generate design artifacts from the feature specification using the plan template.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Constitution Loading
Load constitution per constitution-loading.md (enforcement mode — extract rules, declare hard gate, halt on violations).
Prerequisites Check
-
Run prerequisites check:
bash .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/check-prerequisites.sh --phase 02 --jsonWindows:
pwsh .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/powershell/check-prerequisites.ps1 -Phase 02 -Json -
Parse JSON for
FEATURE_SPEC,IMPL_PLAN,FEATURE_DIR,BRANCH. If missing spec.md: ERROR. -
If JSON contains
needs_selection: true: present thefeaturesarray as a numbered table (name and stage columns). Follow the options presentation pattern in conversation-guide.md. After user selects, run:bash .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/set-active-feature.sh --json <selection>Windows:
pwsh .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/powershell/set-active-feature.ps1 -Json <selection>Then re-run the prerequisites check (item 1 of this section).
Spec Quality Gate
MANDATORY on every run (including re-runs when plan.md already exists) — you MUST complete this gate and report the results before proceeding to the Execution Flow. Do NOT skip this section.
Validate spec.md and output the results:
- Requirements: count FR-XXX patterns (ERROR if 0, WARNING if <3)
- Measurable criteria: scan for numeric values, percentages, time measurements (WARNING if none found — report which SC-XXX lack measurable values)
- Unresolved clarifications: search for
[NEEDS CLARIFICATION]— ask whether to proceed with assumptions - User story coverage: verify each story has acceptance scenarios
- Cross-references: check for orphan requirements not linked to stories
What ships with it
35 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/conversation-guide.md 2.2 KB
- references/formatting-guide.md 3.9 KB
- references/model-recommendations.md 2.5 KB
- references/phase-separation-rules.md 1.6 KB
- references/tessl-tile-discovery.md 2.3 KB
- scripts/bash/check-prerequisites.sh 29 KB runs code
- scripts/bash/common.sh 25 KB runs code
- scripts/bash/generate-dashboard-safe.sh 1.8 KB runs code
- scripts/bash/next-step.sh 14 KB runs code
- scripts/bash/set-active-feature.sh 3.2 KB runs code
- scripts/bash/update-agent-context.sh 8.4 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/check-prerequisites.ps1 23 KB runs code
- scripts/powershell/common.ps1 14 KB runs code
- scripts/powershell/generate-dashboard-safe.ps1 1.8 KB runs code
- scripts/powershell/next-step.ps1 11 KB runs code
- scripts/powershell/set-active-feature.ps1 2.6 KB runs code
- scripts/powershell/update-agent-context.ps1 12 KB runs code
- templates/agent-file-template.md 1.2 KB
- templates/plan-template.md 3.3 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.
- 6d ago First seen · 214 lines · 69 tokens per session scan A 3cf77fc6590e
iikit-02-plan is a skill published in the GitHub repository intent-integrity-chain/kit (47 stars, last pushed 3mo ago), licensed MIT. It adds 69 tokens to every session and 2,236 once invoked, about $0.0003 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…