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 oalders/kitchen-sink --skill working-with-dist-zillagit clone --depth 1 https://github.com/oalders/kitchen-sinkWrote 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/oalders/kitchen-sink/working-with-dist-zilla)<a href="https://agentmods.dev/skills/oalders/kitchen-sink/working-with-dist-zilla"><img src="https://agentmods.dev/badge/skills/oalders/kitchen-sink/working-with-dist-zilla/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/oalders/kitchen-sink/working-with-dist-zilla"><img src="https://agentmods.dev/badge/skills/oalders/kitchen-sink/working-with-dist-zilla.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.00039 | $0.03696 |
| Opus 5 | $0.00019 | $0.01848 |
| Sonnet 5 | $0.00008 | $0.00739 |
| Haiku 4.5 | $0.00004 | $0.00370 |
Grade C, and why
working-with-dist-zilla scanned grade C with 1 finding 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 10d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf <dist-name>-*/ <dist-name>-*.tar.gz How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working with Dist::Zilla Repositories
Overview
Dist::Zilla (dzil) is a meta-tool that builds CPAN distributions from a dist.ini declaration. Many of its behaviors are stable across projects but invisible to anyone who hasn't been bitten — there's no "the docs say so" moment, you just learn by getting them wrong. This skill captures those patterns so you apply them on the first pass instead of discovering each one in an implementer/reviewer loop.
Worked example that surfaced these patterns in sequence: oalders/lwp-consolelogger#56 (Code::TidyAll → precious migration).
When to Use
Use this skill when:
- The repo contains a
dist.inifile at its root - The user mentions
dzil,Dist::Zilla,@Author::*bundles,cpanfile, orMETA.json - You are editing prereqs, swapping plugins, or preparing a release
- A
dzil buildoutput is producing diff noise or unexpected warnings
Don't use when:
- The repo is a plain
ExtUtils::MakeMaker/Module::Builddistribution with nodist.ini - Work is unrelated to packaging (e.g. editing only
lib/source code without touching prereqs or build config)
Workflow
digraph dzil {
"Repo orientation" [shape=box];
"Editing prereqs?" [shape=diamond];
"Decide PluginRemover vs RemovePrereqs" [shape=box];
"Apply edits to dist.ini" [shape=box];
"Run dzil build" [shape=box];
"Decide commit vs revert" [shape=box];
"Run dzil test --release --author" [shape=box];
"Tests pass?" [shape=diamond];
"Fix warnings (e.g. .mailmap)" [shape=box];
"Commit" [shape=box];
"Repo orientation" -> "Editing prereqs?";
"Editing prereqs?" -> "Decide PluginRemover vs RemovePrereqs" [label="yes"];
"Editing prereqs?" -> "Run dzil build" [label="no"];
"Decide PluginRemover vs RemovePrereqs" -> "Apply edits to dist.ini";
"Apply edits to dist.ini" -> "Run dzil build";
"Run dzil build" -> "Decide commit vs revert";
"Decide commit vs revert" -> "Run dzil test --release --author";
"Run dzil test --release --author" -> "Tests pass?";
"Tests pass?" -> "Fix warnings (e.g. .mailmap)" [label="warnings"];
"Fix warnings (e.g. .mailmap)" -> "Run dzil build";
"Tests pass?" -> "Commit" [label="clean"];
}
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.
- 10d ago First seen · 246 lines · 39 tokens per session scan C 02e599728c52
working-with-dist-zilla is a skill published in the GitHub repository oalders/kitchen-sink (4 stars, last pushed 10d ago), licensed MIT. It adds 39 tokens to every session and 3,696 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for…
platform-detection
Identify a .NET project's test platform, framework, command mode, and SDK-style vs classic project system. Use only for "which test platform/framework?", "VSTest or MTP?", or "what runner does this project use?", including bridge settings, UseVSTest opt-outs, and incompatible or conflicting VSTest/MTP configuration.…
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
omh-rust
This is a Hermes-native rust workflow skill.
axiom-concurrency
Use when writing ANY async code, actors, threads, or seeing ANY concurrency error. Covers Swift 6 concurrency, @MainActor, Sendable, data races, async/await patterns.