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 stark-ai-de/agent-skills --skill issue-plan-slicergit clone --depth 1 https://github.com/stark-ai-de/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/stark-ai-de/agent-skills/issue-plan-slicer)<a href="https://agentmods.dev/skills/stark-ai-de/agent-skills/issue-plan-slicer"><img src="https://agentmods.dev/badge/skills/stark-ai-de/agent-skills/issue-plan-slicer/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/stark-ai-de/agent-skills/issue-plan-slicer"><img src="https://agentmods.dev/badge/skills/stark-ai-de/agent-skills/issue-plan-slicer.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.00055 | $0.00685 |
| Opus 5 | $0.00028 | $0.00342 |
| Sonnet 5 | $0.00011 | $0.00137 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
issue-plan-slicer 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Plan Slicer
Goal
Turn a broad plan into small, ordered, independently reviewable work items that an agent or maintainer can execute safely.
When to use
- The user asks to split a spec, roadmap item, issue, PRD, or migration into tasks.
- Work needs GitHub issue drafts, local markdown tasks, or agent-ready implementation slices.
- Dependencies, acceptance criteria, and validation need to be made explicit.
When not to use
- The user wants immediate implementation of a narrow task.
- The plan is still too ambiguous to slice and needs product discovery first.
- The user asks for live issue creation but has not authorized tracker mutations.
Inputs to inspect
- The source spec, issue, PRD, roadmap item, or conversation context.
- Existing
docs/agents/issue-tracker.md,docs/agents/triage-labels.md, anddocs/agents/validation.mdwhen present. - Existing issue templates and labels under
.github/. - Relevant ADRs and domain docs for boundaries and terminology.
Workflow
- Identify the desired outcome and non-goals.
- Extract dependencies, risky assumptions, validation commands, and docs impact.
- Split work into vertical slices that can be reviewed independently.
- Mark blockers and sequencing; avoid slices that require hidden context from prior tasks.
- Draft each issue with title, scope, acceptance criteria, validation, and out-of-scope notes.
- If the issue tracker is unknown, produce local markdown drafts instead of tracker-specific commands.
- Ask before creating, labeling, assigning, or closing live issues.
Safety rules
- Do not mutate issue trackers without explicit user authorization.
- Do not create vague tasks such as "clean up code" without acceptance criteria.
- Do not hide critical dependencies in prose; make them part of the slice.
- Do not assume labels or project boards that are not documented.
References
Use downstream docs/agents/issue-tracker.md and docs/agents/triage-labels.md as hard dependencies for tracker-specific output. If they are missing, default to local markdown issue drafts.
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 · 84 lines · 55 tokens per session scan A dda3b99ce53a
issue-plan-slicer is a skill published in the GitHub repository stark-ai-de/agent-skills (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 55 tokens to every session and 685 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 skills, from other repositories
workspace
Multi-repo workspace coordinator for shared team context. Initialize .adlc/ structure, configure .gitignore, discover child repos, link them as Git submodules, and audit workspace health. Use --init for first-time setup, default mode for ongoing auditing.
product-roadmap
Track milestone progress across four layers of truth — decision state (PDR status), execution state (live issue tracker via MCP), evidence state (code-vs-PDR verification), and gate state (milestone gates). Shows honest completion, done-means warnings, and updates status only when all layers are green. Use for weekly…
product-clarify
Refine and validate Product Decision Records through targeted clarification questions. Review PDR completeness, detect conflicts, approve decisions, and update status to Accepted. Use before /product-implement.
status
Show active or recent Claude Code jobs in this repository, or detailed status for a specific job id. Args: [job-id], --wait, --timeout-ms , --poll-interval-ms , --all. Use for tracked-job inspection, not setup or result retrieval.
session-close
Close a coding-agent session with durable repository state, proportional verification, documentation reconciliation, and a useful handoff. Use when the user says close out, wrap up, end session, session report, doc sync, preserve work, or asks for a final commit and push before stopping.
completion-report
Write a completion report with files changed, tests run, results, skipped checks, docs updated, remaining risks, and release readiness notes. Use when recording evidence that a task or feature is complete and ready for review.