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 kelp/agent-plugins/plugin install zig-claude-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/kelp/agent-plugins/zig-init)<a href="https://agentmods.dev/skills/kelp/agent-plugins/zig-init"><img src="https://agentmods.dev/badge/skills/kelp/agent-plugins/zig-init/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/skills/kelp/agent-plugins/zig-init"><img src="https://agentmods.dev/badge/skills/kelp/agent-plugins/zig-init.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.00091 | $0.00657 |
| Opus 5.5 | $0.00036 | $0.00263 |
| Sonnet 5.5 | $0.00018 | $0.00131 |
| Haiku 4.5 | $0.00009 | $0.00066 |
Grade A, and why
zig-init 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 1mo 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/zig-init
Add Zig training corrections to this project's CLAUDE.md. The plugin supports both 0.15.x and 0.16.x; this skill detects the target version and appends the matching fragment.
Procedure
1. Detect Zig version
Run the detection helper:
${CLAUDE_PLUGIN_ROOT}/scripts/detect-zig-version.sh
It prints 0.15 or 0.16 based on (in order): the project's
build.zig.zon .minimum_zig_version field, then zig version if zig is on PATH, then a default of 0.16.
Capture the output as $VERSION.
2. Read the version-specific fragment
Read the file at:
${CLAUDE_PLUGIN_ROOT}/docs/$VERSION/claude-md-fragment.md
This contains the corrections formatted as a CLAUDE.md section matched to the detected version. If the file is missing, report the error to the user and stop -- do not proceed.
3. Check current CLAUDE.md
Each fragment opens with a version-specific marker heading:
0.15fragment:## Zig 0.15.x Training Corrections0.16fragment:## Zig 0.16.x Training Corrections
Branch on the detected version:
- If no
CLAUDE.mdexists in the project root, create one with just a# CLAUDE.mdheader followed by the fragment content. - If
CLAUDE.mdalready contains the version-specific marker, report "Zig $VERSION.x corrections already present" and stop. - If
CLAUDE.mdcontains the other version's marker (e.g. the project was previously targeting 0.15 and is now 0.16), report "CLAUDE.md has corrections for the other Zig version ($OTHER); manual review needed before swapping" and stop — do not silently overwrite. - Otherwise append the fragment content to the end of the file. Ensure a blank line separates the existing content from the fragment.
4. Report result
Tell the user what you did:
- "Created CLAUDE.md with Zig $VERSION.x corrections"
- "Added Zig $VERSION.x corrections to existing CLAUDE.md"
- "Zig $VERSION.x corrections already present in CLAUDE.md"
- "CLAUDE.md targets the other Zig version; manual review needed before swapping" (with current marker named)
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.
- 1mo ago First seen · 77 lines · 91 tokens per session scan A 9bdf5a721a2f
zig-init is a skill published in the GitHub repository kelp/agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 657 once invoked, about $0.0004 per session on Opus 5.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
better-auth
Skill for integrating Better Auth - comprehensive TypeScript authentication framework for Cloudflare D1, Next.js, Nuxt, and 15+ frameworks. Use when adding auth, encountering D1 adapter errors, or implementing OAuth/2FA/RBAC features.
bun-bundler
This skill should be used when the user asks about "bun build", "Bun.build", "bundling with Bun", "code splitting", "tree shaking", "minification", "sourcemaps", "bundle optimization", "esbuild alternative", "building for production", "bundling TypeScript", "bundling for browser", "bundling for Node", or…
bun-ffi
This skill should be used when the user asks about "bun:ffi", "foreign function interface", "calling C from Bun", "native libraries", "dlopen", "shared libraries", "calling native code", or integrating C/C++ libraries with Bun.
bun-hot-reloading
Use when implementing hot reloading with Bun (--hot, --watch), HMR, or automatic code reloading during development. Covers watch mode, hot mode, and HTTP server reload.
cloudflare-workers-multi-lang
Multi-language Workers development with Rust, Python, and WebAssembly. Use when building Workers in languages other than JavaScript/TypeScript, or when integrating WASM modules for performance-critical code.
dotnet-analyzers
Run dotnet format to fix code style and analyzer diagnostics (IDE0005, CA, SA). Use when fixing unnecessary usings, code style violations, analyzer warnings, or verifying format compliance.