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 rockcrafters/mason --skill chisel-releasesgit clone --depth 1 https://github.com/rockcrafters/masonWrote 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/rockcrafters/mason/chisel-releases)<a href="https://agentmods.dev/skills/rockcrafters/mason/chisel-releases"><img src="https://agentmods.dev/badge/skills/rockcrafters/mason/chisel-releases.svg" alt="Measured on agentmods" 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.00102 | $0.00816 |
| Opus 5 | $0.00051 | $0.00408 |
| Sonnet 5 | $0.00020 | $0.00163 |
| Haiku 4.5 | $0.00010 | $0.00082 |
Grade A, and why
chisel-releases 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 7d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
chisel-releases
Cross-agent skill for working on canonical/chisel-releases.
Self-contained: the same skill directory drives claude code, pi, opencode, copilot, and codex.
Where things live
You work inside a checkout of canonical/chisel-releases -- your current working
directory. Every repo path you read or write -- slices/<pkg>.yaml,
tests/spread/..., chisel.yaml, sibling SDFs -- is relative to this checkout,
exactly as written.
Paths below (commands/, shared/, scripts/, schemas/) are relative to this
skill's own directory instead -- the one holding this SKILL.md. They are
read-only.
Layout
commands/-- command workflows: markdown to read and follow, not executable scriptsshared/CHISEL.md-- reference (format, branch model, schema versions, naming, sources of truth). NOTE: in the mason source repo this file lives atmason/_shared/CHISEL.md; the installer materialises it here.scripts/-- runnable helpers:orientation,deb-list.py(inspect a .deb;--sdfemits a draft SDF),try-cut,scaffold-test.py(emit a spread test skeleton),check-slice.py(deterministic SDF linter),check-test.py(binary test-coverage check),check-diff.py(append-only regression check),review-diff.py(runs all three over a PR diff)schemas/commands.manifest.yaml-- command index (name -> file)
Orient first
Before anything else, run scripts/orientation [<package>]. It prints --
deterministically -- your working dir, this skill's own dir, the target release
- manifest format parsed from
chisel.yaml, and which tools are available here (chisel,dpkg-deb,spread,uv, ...) so you know upfront what you can run. Treat its output as ground truth; don't infer any of it. Then readshared/CHISEL.mdfor format and conventions.
Commands
write-slice and review-slice are not standalone slash commands -- only /chisel-releases is registered. select a command from the invocation:
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- commands/review-slice.md 11 KB
- commands/write-slice.md 27 KB
- schemas/commands.manifest.yaml 819 B
- scripts/check-diff.py 5.8 KB runs code
- scripts/check-slice.py 16 KB runs code
- scripts/check-test.py 5.3 KB runs code
- scripts/deb-list.py 15 KB runs code
- scripts/orientation 2.5 KB
- scripts/review-diff.py 3.7 KB runs code
- scripts/scaffold-test.py 4.8 KB runs code
- scripts/try-cut 1.8 KB
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.
- 7d ago First seen · 55 lines · 102 tokens per session scan A b91804cb6d9f
chisel-releases is a skill published in the GitHub repository rockcrafters/mason (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 102 tokens to every session and 816 once invoked, about $0.0005 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…