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-07-implementnpx skills add intent-integrity-chain/kit --skill iikit-07-implementgit 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-07-implement)<a href="https://agentmods.dev/skills/intent-integrity-chain/kit/iikit-07-implement"><img src="https://agentmods.dev/badge/skills/intent-integrity-chain/kit/iikit-07-implement.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.00083 | $0.02972 |
| Opus 5 | $0.00042 | $0.01486 |
| Sonnet 5 | $0.00017 | $0.00594 |
| Haiku 4.5 | $0.00008 | $0.00297 |
Grade A, and why
iikit-07-implement 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 3d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intent Integrity Kit Implement
Process steps in order. Do not skip ahead.
Execute the implementation plan by processing all tasks in tasks.md.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Windows: Replace
bash …/iikit-core/scripts/bash/*.shwithpwsh …/iikit-core/scripts/powershell/*.ps1(same flags,-PascalCase).
Constitution Loading
Load constitution per constitution-loading.md (enforcement mode — extract rules, declare hard gate, validate before every file write).
Prerequisites Check
- Run:
bash .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/check-prerequisites.sh --phase 07 --json - Parse for
FEATURE_DIRandAVAILABLE_DOCS. If missing tasks.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:
Then re-run the prerequisites check (item 1 of this section).bash .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/set-active-feature.sh --json <selection>
Commit Strategy
Ask the user to choose a commit strategy before starting:
| Strategy | Description |
|---|---|
| A) Per-task (default) | One git commit per completed task. Clean, bisectable history mapping each commit to a task ID. |
| B) Batch | Commits per phase (Setup, Foundational, each User Story, Polish) — typically 4–6 commits. Faster; commits don't map 1:1 to task IDs. |
Default to A if user doesn't respond. Apply the chosen strategy throughout.
Pre-Implementation Validation
Bugfix detection: if every unchecked task has a T-B prefix, this is a bugfix-only run — relaxed gates below.
Standard mode: Verify artifact completeness (constitution, spec, plan, tasks, checklists), cross-artifact consistency (FR-XXX → tasks, tech stack → file paths), and checklist completion (all 100% or ask user). Report READY or BLOCKED.
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/ignore-patterns.md 1.2 KB
- references/model-recommendations.md 2.5 KB
- references/parallel-execution.md 7.8 KB
- references/tessl-integration.md 4.6 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/testify-tdd.sh 24 KB runs code
- scripts/bash/verify-step-quality.sh 24 KB runs code
- scripts/bash/verify-steps.sh 13 KB runs code
- scripts/bash/verify-test-execution.sh 6.8 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/next-step.ps1 11 KB runs code
- scripts/powershell/testify-tdd.ps1 22 KB runs code
- 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.
- 3d ago First seen · 264 lines · 83 tokens per session scan A 146a8069dddc
iikit-07-implement is a skill published in the GitHub repository intent-integrity-chain/kit (47 stars, last pushed 3mo ago), licensed MIT. It adds 83 tokens to every session and 2,972 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…