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/dallay/agents-skills/zig-developmentnpx skills add dallay/agents-skills --skill zig-developmentgit clone --depth 1 https://github.com/dallay/agents-skillsWhat 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.00050 | $0.02892 |
| Opus 5 | $0.00025 | $0.01446 |
| Sonnet 5 | $0.00010 | $0.00578 |
| Haiku 4.5 | $0.00005 | $0.00289 |
Grade A, and why
zig-development 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 2d 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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zig Development
Production patterns for Zig systems programming, covering the build system, comptime, error handling, allocators, testing, and C interop.
When to Use This Skill
- Starting or structuring a Zig project
- Working with the
build.zigbuild system - Using comptime for compile-time computation
- Handling errors with error unions
- Choosing and using allocators
- Writing tests in Zig
- Interfacing with C libraries
Core Concepts
1. Project Layout
myapp/
├── src/
│ ├── main.zig # Entry point
│ ├── lib.zig # Library root (public API)
│ ├── parser.zig
│ └── network/
│ ├── client.zig
│ └── protocol.zig
├── build.zig # Build configuration
├── build.zig.zon # Package manifest (dependencies)
└── README.md
2. Key Principles
| Principle | Zig Idiom |
|---|---|
| No hidden control | No hidden allocations, no operator overloading |
| Explicit errors | Error unions force handling at every call site |
| Comptime | Generics and metaprogramming via compile-time eval |
| Manual memory | Choose allocator per context; no GC |
| C interop | Direct @cImport with zero overhead |
Quick Start
# Initialize a new project
zig init
# Build
zig build
# Build and run
zig build run
# Run tests
zig build test
# Run a single file
zig run src/main.zig
# Format
zig fmt src/
Patterns
Pattern 1: Build System (build.zig)
const std = @import("std");
pub fn build(b: *std.Build) void {
const target = b.standardTargetOptions(.{});
const optimize = b.standardOptimizeOption(.{});
// Library
const lib = b.addStaticLibrary(.{
.name = "mylib",
.root_source_file = b.path("src/lib.zig"),
.target = target,
.optimize = optimize,
});
// Link C library
lib.linkSystemLibrary("sqlite3");
lib.linkLibC();
b.installArtifact(lib);
// Executable
const exe = b.addExecutable(.{
.name = "myapp",
.root_source_file = b.path("src/main.zig"),
.target = target,
.optimize = optimize,
});
exe.linkLibrary(lib);
b.installArtifact(exe);
// Run step
const run_cmd = b.addRunArtifact(exe);
run_cmd.step.dependOn(b.getInstallStep());
if (b.args) |args| {
run_cmd.addArgs(args);
}
const run_step = b.step("run", "Run the application");
run_step.dependOn(&run_cmd.step);
// Tests
const lib_tests = b.addTest(.{
.root_source_file = b.path("src/lib.zig"),
.target = target,
.optimize = optimize,
});
const run_lib_tests = b.addRunArtifact(lib_tests);
const test_step = b.step("test", "Run unit tests");
test_step.dependOn(&run_lib_tests.step);
}
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.
- 2d ago First seen · 439 lines · 50 tokens per session scan A 1cdd1e2667b8
zig-development is a skill published in the GitHub repository dallay/agents-skills (2 stars, last pushed 10d ago), licensed MIT. It adds 50 tokens to every session and 2,892 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
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…