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-corenpx skills add intent-integrity-chain/kit --skill iikit-coregit 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-core)<a href="https://agentmods.dev/skills/intent-integrity-chain/kit/iikit-core"><img src="https://agentmods.dev/badge/skills/intent-integrity-chain/kit/iikit-core.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.00116 | $0.02467 |
| Opus 5 | $0.00058 | $0.01234 |
| Sonnet 5 | $0.00023 | $0.00493 |
| Haiku 4.5 | $0.00012 | $0.00247 |
Grade A, and why
iikit-core 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intent Integrity Kit Core
This skill is an action router — pick the step that matches the user's intent and execute only that step. Do not run other steps; do not parallelize.
Core skill providing project initialization, status checking, feature selection, scaffolding removal, and workflow help.
User Input
$ARGUMENTS
Parse the user input to determine which subcommand to execute. Available subcommands map to steps below: init (Step 1), status (Step 2), use (Step 3), uninit (Step 4), help (Step 5). If no subcommand is provided, execute Step 5 (help).
Working directory: All script paths are relative to the project root (the directory containing
tessl.jsonor.tessl/). If a script path doesn't resolve, search with:find . -path "*/iikit-core/scripts/bash/<script>.sh" 2>/dev/null || find ~/.tessl -path "*/iikit-core/scripts/bash/<script>.sh" 2>/dev/null
Step 1 — init
Initialize intent-integrity-kit in the current directory. Handles the full project bootstrap: git init, optional GitHub repo creation, or cloning an existing repo. Optionally seeds the project backlog from an existing PRD/SDD document.
Argument parsing: The $ARGUMENTS after init may include an optional reference to a PRD/SDD document the user wants to seed from (e.g., /iikit-core init ./docs/prd.md). If present, store it as prd_source for use in the "Seed backlog from PRD" sub-action. The PRD-seeding flow is user-opt-in only and follows the consent model documented in prd-seeding.md.
Sub-procedure (perform in order):
- Detect environment, initialize hooks, check premise:
Parse JSON forbash .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/bash/init-full.sh --json # Windows: pwsh .tessl/plugins/tessl-labs/intent-integrity-kit/skills/iikit-core/scripts/powershell/init-full.ps1 -Jsongit(environment),init(hooks), andpremise(validation) sections.git.gh_availablefalse → suggest installing GitHub CLIinit.git_user_configuredfalse → ask user for name/email, rungit config
What ships with it
60 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/ambiguity-taxonomies.md 2.5 KB
- references/checklist-gate.md 737 B
- references/ci-assertion-verification.md 1.4 KB
- references/constitution-loading.md 1.5 KB
- references/conversation-guide.md 2.2 KB
- references/formatting-guide.md 3.9 KB
- references/help-reference.md 1.3 KB
- references/hook-chaining.md 5.0 KB
- references/model-recommendations.md 2.5 KB
- references/phase-separation-rules.md 1.6 KB
- references/prd-seeding.md 3.3 KB
- scripts/bash/bugfix-helpers.sh 6.3 KB runs code
- scripts/bash/check-hook-bypass.sh 1.6 KB runs code
- scripts/bash/check-prerequisites.sh 30 KB runs code
- scripts/bash/common.sh 26 KB runs code
- scripts/bash/create-new-feature.sh 11 KB runs code
- scripts/bash/fetch-tile-evals.sh 4.5 KB runs code
- scripts/bash/generate-dashboard-safe.sh 2.0 KB runs code
- scripts/bash/git-setup.sh 3.3 KB runs code
- scripts/bash/init-full.sh 1.9 KB runs code
- scripts/bash/init-project.sh 9.6 KB runs code
- scripts/bash/next-step.sh 14 KB runs code
- scripts/bash/post-commit-hook.sh 6.2 KB runs code
- scripts/bash/post-phase.sh 2.8 KB runs code
- scripts/bash/pre-commit-hook.sh 22 KB runs code
- scripts/bash/session-context-hook-gemini.sh 1.7 KB runs code
- scripts/bash/session-context-hook.sh 1.2 KB runs code
- scripts/bash/set-active-feature.sh 3.2 KB runs code
- scripts/bash/setup-bdd.sh 7.6 KB runs code
- scripts/bash/setup-plan.sh 139 B runs code
- scripts/bash/setup-unix-links.sh 6.6 KB runs code
- scripts/bash/testify-tdd.sh 24 KB runs code
- scripts/bash/uninit.sh 10 KB runs code
- scripts/bash/update-agent-context.sh 8.4 KB runs code
- scripts/bash/validate-premise.sh 6.5 KB runs code
- scripts/bash/verify-assertion-integrity.sh 8.6 KB runs code
- scripts/bash/verify-bdd.sh 2.1 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 219 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.5 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/package.json 20 B
- scripts/dashboard/src/parser.js 48 KB runs code
- scripts/dashboard/src/pipeline.js 7.2 KB runs code
- scripts/dashboard/src/planview.js 9.2 KB runs code
- scripts/dashboard/src/public/index.html 219 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 226 KB runs code
- scripts/powershell/bugfix-helpers.ps1 4.4 KB runs code
- scripts/powershell/check-prerequisites.ps1 24 KB runs code
- scripts/powershell/common.ps1 16 KB runs code
- scripts/powershell/create-new-feature.ps1 11 KB runs code
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 · 159 lines · 116 tokens per session scan A 755e2a5432a2
iikit-core is a skill published in the GitHub repository intent-integrity-chain/kit (47 stars, last pushed 3mo ago), licensed MIT. It adds 116 tokens to every session and 2,467 once invoked, about $0.0006 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…