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 markoblogo/abvx-agent-skills --skill plan-to-issuesgit clone --depth 1 https://github.com/markoblogo/abvx-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/markoblogo/abvx-agent-skills/plan-to-issues)<a href="https://agentmods.dev/skills/markoblogo/abvx-agent-skills/plan-to-issues"><img src="https://agentmods.dev/badge/skills/markoblogo/abvx-agent-skills/plan-to-issues.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.1 | $0.00065 | $0.00399 |
| Opus 5 | $0.00032 | $0.00199 |
| Sonnet 5 | $0.00013 | $0.00080 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
plan-to-issues 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 8d 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
Plan To Issues
Turn a plan into vertical slices that can actually be picked up and shipped.
Workflow
- Gather the parent artifact: PRD, plan, or spec.
- Explore the repo only enough to understand the real seams.
- Break the work into thin vertical slices:
- end-to-end;
- verifiable on their own;
- blocker-aware;
- small enough to review.
- Classify slices:
- agent-ready;
- human-required;
- blocked by decision or external dependency.
- Show the proposed breakdown and adjust granularity before publishing or writing it down.
Slice Rules
- Prefer many thin slices over a few thick ones.
- Each slice should cut through the relevant layers, not isolate one layer.
- A completed slice should be demoable, testable, or reviewable on its own.
Output
For each slice include:
- title;
- type;
- what to build;
- acceptance criteria;
- blockers;
- parent reference when relevant.
Rules
- Do not output horizontal slices like "DB layer", "API layer", "UI layer" unless the parent work truly is infrastructure-only.
- Keep issue-tracker-neutral language; publish to a tracker only if the workflow calls for it.
- If the plan is still fuzzy, route back to
spec-to-prdor grilling first.
Final Report
Summarize the slice graph, identify the first executable slice, and note what still needs a human decision.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 55 lines · 65 tokens per session scan A 06af74e52ecf
plan-to-issues is a skill published in the GitHub repository markoblogo/abvx-agent-skills (16 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 399 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-30.
Other skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
problem-management
Manage ServiceNow problems — create from linked incidents, proactive pattern detection, RCA with 5-Whys, knownerror workarounds (KEDB), KEDB search by CI/category/keywords, and permanent-fix linkage to changes.
incident-management
Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
sap-session
A guided evidence-review process for diagnosing SAP operations without direct access to the live system, with a person collecting evidence and the agent reviewing it.
defect
A command for registering a software defect, meaning behavior that does not work as intended, and creating a task to fix it. The defect and its fix task receive tracked IDs and are stored in the project's backlog and task folders.