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/jobshwang/skills/slice-specgit clone --depth 1 https://github.com/JobsHwang/skillsWrote 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/jobshwang/skills/slice-spec)<a href="https://agentmods.dev/commands/jobshwang/skills/slice-spec"><img src="https://agentmods.dev/badge/commands/jobshwang/skills/slice-spec.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.00022 | $0.00274 |
| Opus 5 | $0.00011 | $0.00137 |
| Sonnet 5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
slice-spec 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.
What it actually says
The user explicitly invoked /slice-spec.
Invocation arguments: $ARGUMENTS
Slice Spec
Split only when splitting increases delivery speed or feedback quality.
- Read the parent spec and inspect enough of the repository to understand real seams.
- If the work is one coherent deliverable that fits a single implementation session, say that slicing is unnecessary and stop without creating files.
- Otherwise create end-to-end vertical slices. Each slice should produce observable behavior and its own verification signal.
- Prefer risk-first tracer bullets that validate uncertain contracts early. Do not default to separate frontend, backend, database, or test-only slices.
- Declare blocking edges explicitly and keep independent slices parallelizable.
- Preserve cross-layer contract ownership and compatibility in every affected slice.
Write files beside the parent spec, normally .scratch/<feature>/slices/01-<slug>.md, using references/slice-template.md. Follow an existing local convention when one exists. Do not create an issue tracker, task state machine, journal, or implementation.
Report the dependency order, why each boundary is useful, and the recommended first slice. The next action is direct implementation unless the user explicitly chooses another workflow.
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 · 23 lines · 22 tokens per session scan A 379aa083526b
slice-spec is a command published in the GitHub repository JobsHwang/skills (2 stars, last pushed 2d ago), licensed MIT. It adds 22 tokens to every session and 274 once invoked, about $0.0001 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
git
Git operations with intelligent commit messages and workflow optimization.
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.