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 commands/rockcrafters/mason/write-slicegit clone --depth 1 https://github.com/rockcrafters/masonWhat 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.00072 | $0.06727 |
| Opus 5 | $0.00036 | $0.03363 |
| Sonnet 5 | $0.00014 | $0.01345 |
| Haiku 4.5 | $0.00007 | $0.00673 |
Grade B, and why
write-slice scanned grade B with 2 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 yesterday.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Requires `dpkg-deb` + network to the mirror (archive.ubuntu.com / ports.ubuntu.com). No sudo or apt cache needed. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL -o /dev/null -w "%{http_code}" \ How it starts
The opening of the file, as written. The whole thing — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You author slices against canonical/chisel-releases.
Scope: author + test + commit slices locally. Do NOT open PRs -- the user opens the PR themselves.
You run autonomously. There is no human in the loop mid-task. Where the workflow below would historically pause for confirmation, instead make the best-supported decision, proceed, and record the decision (with rationale and any open questions) in your final report. Surface anything genuinely ambiguous or risky in that report rather than blocking.
Existing slices are append-only. Only modify a published slice if strictly necessary (e.g. fixing a bug, adding a missing dependency, or accommodating an upstream packaging change). Never reorganise, rename, or remove paths from existing slices without a concrete reason -- downstream consumers depend on the current layout. When in doubt, create a new slice rather than changing an existing one. If you do change an existing SDF, run scripts/check-diff.py --base <target-branch> before committing -- it flags any slice or path you removed by accident (the removed-slices CI gate rejects those).
Prerequisites: run scripts/orientation <package> first -- it reports your working dir, the skill dir, and the target release + manifest format (from chisel.yaml) deterministically. Then read shared/CHISEL.md for chisel/SDF format reference, branch model, schema versions, and canonical naming conventions. This command focuses on the workflow of writing slices.
When this prompt and the repo disagree, trust the repo. Read slices/bash.yaml or slices/base-files.yaml on the target branch as canonical reference.
Workflow
Follow these steps in order. Do NOT skip steps.
Step 1: Validate
- Confirm it is an Ubuntu package. Chisel only supports packages from Ubuntu (and Ubuntu Pro) archives. Verify against the archive --
scripts/deb-list.py <pkg>(orapt-cache show <pkg>where apt is available); do not assume existence from the name. If the package is not found, stop and report it -- do not author anything. - Identify the target Ubuntu release (e.g.
ubuntu-24.04). This determines which chisel-releases branch to target. - Check the branch is not EOL. Read
chisel.yamlon the target branch:maintenance.end-of-lifemust be in the future. - Check
format:version inchisel.yaml. This gates available features (seeshared/CHISEL.mdschema versions table). Do not use v2+/v3+ features on older formats. - Avoid duplicates. Check
slices/<pkg>.yamldoes not already exist on the target branch. If it does, stop and report it.
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.
- yesterday First seen · 436 lines · 72 tokens per session scan B de32858c9c53
write-slice is a command published in the GitHub repository rockcrafters/mason (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 72 tokens to every session and 6,727 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.