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 kambleakash0/agent-skills --skill slice-the-specgit clone --depth 1 https://github.com/kambleakash0/agent-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/skills/kambleakash0/agent-skills/slice-the-spec)<a href="https://agentmods.dev/skills/kambleakash0/agent-skills/slice-the-spec"><img src="https://agentmods.dev/badge/skills/kambleakash0/agent-skills/slice-the-spec/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/kambleakash0/agent-skills/slice-the-spec"><img src="https://agentmods.dev/badge/skills/kambleakash0/agent-skills/slice-the-spec.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.00030 | $0.01253 |
| Opus 5 | $0.00015 | $0.00626 |
| Sonnet 5 | $0.00006 | $0.00251 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
slice-the-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 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.
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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Turn a PRD into Issues
This skill takes a clarified PRD and turns it into a small, sharp backlog of vertically sliced GitHub issues. Each issue should be an independently grabbable “tracer bullet” that cuts through all relevant layers end‑to‑end, flushing out unknown unknowns as early as possible.
When to Use
Use this skill when the user:
- Has a PRD or similar spec (possibly created via
/spec-writer) and now wants concrete issues. - Wants to turn “destination” docs into a Kanban board of tasks.
- Needs to break work down so multiple engineers or agents can work in parallel without stepping on each other.
If there is no PRD yet or the requirements are fuzzy, suggest using /grill-me and /spec-writer first.
Concepts
- Vertical slice / tracer bullet: A thin, end‑to‑end piece of functionality that goes through all necessary layers (data, domain, API, UI, etc.), not just one layer in isolation.
- HITL issue: Requires Human‑In‑The‑Loop decisions (design review, stakeholder sign‑off, risky refactor, etc.).
- AFK issue: “Away‑From‑Keyboard” for the human; safe enough for an autonomous agent to implement and merge without human intervention.
Prefer AFK slices where possible, but mark HITL clearly where human judgment is essential.
Workflow
You may compress or skip steps if the context already provides the answer (e.g., the PRD is already loaded and clearly scoped).
-
Locate and understand the PRD
- Find the PRD from the conversation or repository (issue, doc, file).
- Skim to understand: goals, user stories, functional requirements, and explicit non‑goals.
- If multiple PRDs are present, confirm with the user which one to use.
-
Explore the codebase
- Inspect relevant parts of the repo to understand current architecture, major modules, and likely integration points.
- Note any existing patterns you should respect (e.g., existing feature flags, background jobs, notification systems).
-
Draft vertical slices (tracer bullets)
- Break the PRD into a small set of vertical slices, each of which delivers end‑to‑end value and exercises multiple layers of the system.
- Avoid horizontal slices like “set up database tables” or “build all UI components” unless truly necessary; fold those into end‑to‑end slices instead.
- For each slice, decide whether it is HITL or AFK, preferring AFK when risk is low.
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 · 113 lines · 30 tokens per session scan A 298bd8ec3b58
slice-the-spec is a skill published in the GitHub repository kambleakash0/agent-skills (9 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 1,253 once invoked, about $0.0002 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
linear-cli
Use when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write boundaries.
accelo-automation
Automate Accelo tasks via Rube MCP (Composio). Always search tools first for current schemas.
aero-workflow-automation
Automate Aero Workflow tasks via Rube MCP (Composio). Always search tools first for current schemas.
agiled-automation
Automate Agiled tasks via Rube MCP (Composio). Always search tools first for current schemas.
atlassian-automation
Automate Atlassian tasks via Rube MCP (Composio). Always search tools first for current schemas.
bigpicture-io-automation
Automate Bigpicture IO tasks via Rube MCP (Composio). Always search tools first for current schemas.