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 perniemann/pnCore --skill pn-github-vertical-slicesgit clone --depth 1 https://github.com/perniemann/pnCoreWrote 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/perniemann/pncore/pn-github-vertical-slices)<a href="https://agentmods.dev/skills/perniemann/pncore/pn-github-vertical-slices"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-github-vertical-slices/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/perniemann/pncore/pn-github-vertical-slices"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-github-vertical-slices.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.00064 | $0.00844 |
| Opus 5.5 | $0.00026 | $0.00338 |
| Sonnet 5.5 | $0.00013 | $0.00169 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
pn-github-vertical-slices 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 1mo 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub vertical slices
When to use
- After pn-writing-plans or pn-create-prd, when implementation should be tracked as GitHub Issues (parallel agents or humans).
- User asks to “split this plan into Issues”, “vertical slices”, “tracer bullets”, or “one Issue per slice.”
Prerequisites
- GitHub MCP server enabled with at least
context,issues, andlabelstoolsets (addreposif repo metadata is needed). See server configuration. - Repository scope: Infer owner/repo from
git remoteor user-provided URL when ambiguous.
If GitHub MCP is not available: stop and tell the user to enable the official server or fall back to creating Issues manually — do not pretend Issues were created.
Concepts
- Tracer-bullet slice: One thin vertical cut through schema/API/UI/tests — demoable or verifiable on its own. Prefer many thin slices over few thick ones.
- AFK: Can ship without human gate beyond normal review.
- HITL: Blocked on a decision, explicit approval, or design/sign-off.
Replace labels below with your repo’s taxonomy when different.
Instructions
1. Gather input
Use conversation context, an attached plan (docs/plans/…), or a GitHub Issue URL/number if the user references one.
2. Draft slices
Produce slices as numbered candidates. For each slice include:
| Field | Content |
|---|---|
| Title | Short, actionable |
| Type | AFK or HITL |
| Blocked by | None or slice numbers / Issue refs once known |
| Stories covered | References to user stories from source material if present |
Rules:
- Each slice delivers end-to-end behavior, not “layer N only.”
- Order dependencies first: unblockers before blocked work.
3. Confirm with user
Present the list; ask whether granularity, dependencies, and AFK/HITL tagging match expectations. Iterate until approved.
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.
- 1mo ago First seen · 98 lines · 64 tokens per session scan A 75efd09e6dfc
pn-github-vertical-slices is a skill published in the GitHub repository perniemann/pnCore (0 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 844 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
pod-init
Initialize CocoPlus project bundle in the current directory. Creates .cocoplus/ directory structure, copies all templates, initializes AGENTS.md, project.md, flow.json, and creates the initial git commit. Run this once per project before using any other CocoPlus command.
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
jira-execute
Implement a Jira issue, open a pull request, and report the work on the issue. Insert into the prompt of a Jira column rule that does the building.
jira-merge
Land the pull requests a set of Jira issues carry, in order, resolving a conflict when one appears, and move each card on. Insert into the prompt of a run started on a batch of issues, or of a Jira column rule that ships.
handoff-discipline
Use when ending a session, handing a task back to the user, or approaching the context limit with work unfinished -- the next session or engineer must be able to resume the work instantly.
resolve-publish
Commit the validated fix and follow local-only, workflow-owned, or direct PR publication.