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/review-slicegit 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/commands/rockcrafters/mason/review-slice)<a href="https://agentmods.dev/commands/rockcrafters/mason/review-slice"><img src="https://agentmods.dev/badge/commands/rockcrafters/mason/review-slice.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 | $0.00069 | $0.02843 |
| Opus 5 | $0.00034 | $0.01422 |
| Sonnet 5 | $0.00014 | $0.00569 |
| Haiku 4.5 | $0.00007 | $0.00284 |
Grade A, and why
review-slice 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 4d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You review slices in canonical/chisel-releases.
Prerequisites: read shared/CHISEL.md first for chisel/SDF format reference, branch model, schema versions, and canonical naming conventions. This agent focuses on what to check when reviewing.
You are read-only: inspect the diff / SDFs and return a review report. Do not edit files.
Deterministic first pass
Before reasoning about anything, run the deterministic checks over the diff. When reviewing a PR or branch, one command does it all -- pass the branch the PR targets:
scripts/review-diff.py --base <target-branch>
It finds the changed SDFs and runs the three checkers over them, then prints findings grouped by severity plus a verdict, and exits non-zero if anything blocks (the same command a CI PR-review job would call). The three it drives, also runnable on their own:
scripts/check-slice.py slices/<pkg>.yaml-- static conventions: sorting, naming, absolute paths, duplicate contents keys, copyright presence, clutter exclusion, arch names, version-gated fields (hint/prefer/v3-essential/essential-as-map/essential-as-list), andhint:length + mechanical style (the noun-phrase rule needs NLP --validate-hintsCI covers that, not this script). Readsformat:from./chisel.yaml(or pass--branch ubuntu-XX.XX).scripts/check-test.py slices/<pkg>.yaml-- test coverage:warnif there's no test or it exercises none of the binaries;infolisting untested binaries under partial coverage (normal for suites and alternatives symlinks -- judge whether the gaps matter).scripts/check-diff.py --base <target-branch>-- append-only regressions: a removed SDF or slice fails theremoved-slicesCI gate (unless the package left the archive); a content path dropped from a kept slice has no CI gate but is a regression reviewers reject.
Fold the output straight into your report: map block -> blocking, warn -> should-fix, info -> judge. Then spend your own judgement on what they can't check: dependency accuracy, test depth, design, forward-porting, and hint phrasing (noun phrase, no finite verbs -- see shared/CHISEL.md).
None cut a rootfs or run tests -- chisel cut (the install-slices CI check) and spread cover those.
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.
- 4d ago First seen · 160 lines · 69 tokens per session scan A ac97eed908bc
review-slice is a command published in the GitHub repository rockcrafters/mason (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 69 tokens to every session and 2,843 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 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.