Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add assafkip/kipi-system/plugin install kipi-coreWrote 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/commands/assafkip/kipi-system/wiring-check)<a href="https://agentmods.dev/commands/assafkip/kipi-system/wiring-check"><img src="https://agentmods.dev/badge/commands/assafkip/kipi-system/wiring-check/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/commands/assafkip/kipi-system/wiring-check"><img src="https://agentmods.dev/badge/commands/assafkip/kipi-system/wiring-check.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.01798 |
| Opus 5 | $0.00018 | $0.00899 |
| Sonnet 5 | $0.00007 | $0.00360 |
| Haiku 4.5 | $0.00004 | $0.00180 |
Grade A, and why
wiring-check 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 9d 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run a Wiring Check on the work done in this session. Treat "this session" as the
current git diff against the default branch unless the founder specifies
otherwise (e.g., since HEAD~3, or a file list).
Goal: nothing disconnected, unused, unreachable, or half-integrated. If a file was created or edited, prove it is reachable from something that already runs.
Process (required, in order)
1. Enumerate changes
Run:
git diff --name-status origin/main...HEAD
git status --short
List every changed/created/deleted file. Group by kipi category (see matrix below).
2. Map to integration points
For each changed file, state the expected wiring based on its path. Use the
matrix below. If a file doesn't fit any category, call it out — it may be in
the wrong directory per .claude/rules/folder-structure.md.
3. Verify each wire
Use Grep/Glob/Read to prove the connection exists. No assumptions. If verification requires running a script, run it.
4. Fix gaps, then re-verify
If a wire is missing, fix it. Do not leave a "TODO: wire this up" — that is the exact failure mode this command exists to prevent.
5. Output WIRING REPORT
Structure:
- Changes shipped (file list, grouped by category)
- Wiring evidence (file + symbol/line for each connection)
- Verification run (commands executed + results, pass/fail)
- Gaps found and fixed (if any)
- Exceptions (rare; rationale + tracking reference)
- Skeleton propagation status — if this is the skeleton repo
(
kipi-system), confirmkipi update --drywould pick up these changes; if this is an instance repo, note whether the change belongs upstream in the skeleton
Wiring Matrix (kipi-specific)
Check the wires that apply. Do not skip a category because "it looks obvious."
New or edited skill (plugins/*/skills/<name>/SKILL.md)
- SKILL.md has frontmatter with
name,description,license - Skill directory is under a plugin that ships (kipi-core / kipi-ops / kipi-design / kipi-dsse / prd-os)
- Any references in the skill (scripts, refs/) exist at the stated paths
- If auto-invoked, the trigger rule exists in
.claude/rules/*-auto-invoke.mdOR the skill description contains a clear trigger pattern - No duplicate skill name across plugin groups
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.
- 9d ago First seen · 144 lines · 37 tokens per session scan A cdb94a2c54d4
wiring-check is a command published in the GitHub repository assafkip/kipi-system (110 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 1,798 once invoked, about $0.0002 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.