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/kelp/agent-plugins/zig-checknpx skills add kelp/agent-plugins --skill zig-checkgit clone --depth 1 https://github.com/kelp/agent-pluginsWhat 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.00054 | $0.02314 |
| Opus 5 | $0.00027 | $0.01157 |
| Sonnet 5 | $0.00011 | $0.00463 |
| Haiku 4.5 | $0.00005 | $0.00231 |
Grade A, and why
zig-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 yesterday.
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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/zig-check [file]
Audit Zig source files for outdated APIs. The plugin supports
both Zig 0.15.x and 0.16.x; this skill detects the target
version and applies the matching rule set. If a file path is
given, check that file. Otherwise check all *.zig files, in
any directory, that were modified in the current git diff
(staged and unstaged).
Procedure
1. Detect Zig version
Run:
${CLAUDE_PLUGIN_ROOT}/scripts/detect-zig-version.sh
Capture the output as $VERSION (0.15 or 0.16).
2. Determine target files
If argument provided:
- Check only that file
If no argument:
- Run
git diff --name-onlyandgit diff --cached --name-only - Filter to
*.zigfiles, recursively, regardless of directory - If no modified Zig files, report "No modified Zig files to check" and exit
3. Read each target file
Use the Read tool to read the full contents of each file.
4. Apply the version-specific rule set
Search each file for the patterns below. Report each violation with file path, line number, and the specific issue.
Rules that apply to BOTH 0.15.x and 0.16.x
These are wrong on every supported Zig version:
-
Deleted-in-0.15 APIs:
std.io.getStdOut/std.io.getStdErr-- use buffered writer patternusingnamespace-- removed from languageasync/await-- removed from languagestd.BoundedArray-- useArrayListUnmanaged.initBufferstd.json.Parser-- usestd.json.parseFromSlice
-
Renamed APIs (still valid in both versions):
std.mem.tokenize(withoutAny/Scalar/Sequence-- usetokenizeAny,tokenizeScalar, ortokenizeSequence
-
ArrayList without allocator:
.append(,.appendSlice(,.deinit()etc. without allocator as first argument (forArrayListUnmanaged)
-
Ambiguous format strings:
"{}"in print/format calls -- must use{s},{d},{any}, etc.
-
Signed division without builtins:
/or%on runtime signed integer variables -- use@divTrunc,@divFloor,@divExact,@rem,@mod
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.
- yesterday First seen · 226 lines · 54 tokens per session scan A 85dc900460a9
zig-check is a skill published in the GitHub repository kelp/agent-plugins (2 stars, last pushed 9d ago), licensed MIT. It adds 54 tokens to every session and 2,314 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-31.
Other skills, from other repositories
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
shipping-artifacts
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded…
stakeholder-map
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.