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 skills add zuke-build/zuke --skill zuke-setupgit clone --depth 1 https://github.com/zuke-build/zukeWrote 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/zuke-build/zuke/zuke-setup)<a href="https://agentmods.dev/skills/zuke-build/zuke/zuke-setup"><img src="https://agentmods.dev/badge/skills/zuke-build/zuke/zuke-setup/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/zuke-build/zuke/zuke-setup"><img src="https://agentmods.dev/badge/skills/zuke-build/zuke/zuke-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 29 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00082 | $0.03617 |
| Opus 5.5 | $0.00033 | $0.01447 |
| Sonnet 5.5 | $0.00016 | $0.00723 |
| Haiku 4.5 | $0.00008 | $0.00362 |
Grade A, and why
zuke-setup 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up Zuke in a project
Zuke defines builds as a TypeScript class run on Deno. Each target is a
class field; targets reference each other by this.<field> (never strings).
Packages are imported from JSR (jsr:@zuke/...), not npm.
The fast path: zuke setup
The @zuke/cli tool scaffolds everything. Install it once, then run setup in
the target project:
deno install -A -g -n zuke jsr:@zuke/cli # once, globally
zuke setup # in the project root
./zuke # run the build
zuke upgrade # later: update the global CLI
zuke add docker # add a wrapper: jsr:@zuke/docker into deno.json
zuke relock --min-dep-age 0 # regenerate the lock (e.g. to move core forward)
No global install? The same wizard runs directly:
deno run -A jsr:@zuke/cli setup
No Deno at all, on macOS or Linux? brew install zuke-build/tap/zuke installs
the same CLI as a signed standalone binary; zuke setup then works at once, and
the ./zuke launcher it writes installs Deno when the build first runs. Update
that install with brew upgrade zuke, not zuke upgrade (which refuses it). On
Windows, choco install zuke installs the same binary through Chocolatey (not
Authenticode-signed yet, so SmartScreen may warn); update it with
choco upgrade zuke. zuke --version on a terminal shows which install
answered.
setup flags: --dir <path>, --name <ClassName>, --force (overwrite
existing files), --yes (non-interactive), --bootstrap-deno /
--no-bootstrap-deno (which launchers to write — see below; the wizard asks
when interactive, and --yes takes the default, bootstrap), --mcp (also write
.mcp.json registering the build's MCP server, so this agent — and any other
stdio MCP client — can list and run the targets through typed calls;
--allow-run registers it with execution enabled and implies --mcp),
--launcher-name <name> (write the launcher under a different name when a
zuke/ directory already occupies it — a directory collision now fails with an
actionable error instead of silently skipping the launcher). With --mcp, an
MCP client lists and runs the targets through typed calls; without it, the build
is still discoverable through ./zuke --list --json.
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 Changed · +3 lines 6ec19308aa04
- 4d ago Changed · +6 lines ac8944035bb0
- 8d ago Changed · +2 lines 1428ebc9da30
- 9d ago Changed · +6 lines e88b5e87f43a
- 16d ago Changed · +2 lines 6410484444f3
- 25d ago Changed · +43 lines 6fbf7d2c4127
- 1mo ago Changed · +17 lines 700a3eab33ec
- 1mo ago Changed · +7 lines 6498b2be426f
- 1mo ago Changed · +9 lines 09eb9fd51775
- 1mo ago First seen · 156 lines · 82 tokens per session scan A 7c5444a3107d
zuke-setup is a skill published in the GitHub repository zuke-build/zuke (46 stars, last pushed 2d ago), licensed MIT. It adds 82 tokens to every session and 3,617 once invoked, about $0.0003 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-30.
Other skills, from other repositories
turborepo
Configure and troubleshoot Turborepo repositories. Use when working with turbo.json, task pipelines, caching, Remote Cache, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure, or CI workflows.
debug-task
Diagnose and fix moon tasks that are broken, misconfigured, or behaving unexpectedly. Use this skill when a moon task is failing, not running, skipped, hanging, producing stale or wrong output, cached when it shouldn't be, re-running every time, or missing outputs after a cache hit. Also covers pipeline hangs, tasks…
content-hash-cache-pattern
Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
kotlin-tooling-gradle-to-kotlin-toolchain-project
Load when migrating or converting an entire Gradle Kotlin project (build.gradle(.kts), wrapper, libs.versions.toml, buildSrc) to the Kotlin Toolchain, including rewriting CI and replacing Gradle plugins that have no native Toolchain equivalent. Skip for porting one Gradle plugin or general Toolchain work once Gradle…
temps-plugin
Design, build, test, and distribute external Temps plugins with TypeScript/Bun; provide development and local-testing guidance for existing Rust plugins. Use for creating a plugin, adding an embedded console UI or deployment-event automation, testing host permissions and AI, installing from GitHub, or submitting a…