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 n-n-code/n-n-code-skills --skill story-implementation-plannergit clone --depth 1 https://github.com/n-n-code/n-n-code-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/n-n-code/n-n-code-skills/story-implementation-planner)<a href="https://agentmods.dev/skills/n-n-code/n-n-code-skills/story-implementation-planner"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/story-implementation-planner/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/n-n-code/n-n-code-skills/story-implementation-planner"><img src="https://agentmods.dev/badge/skills/n-n-code/n-n-code-skills/story-implementation-planner.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.00065 | $0.03015 |
| Opus 5.5 | $0.00026 | $0.01206 |
| Sonnet 5.5 | $0.00013 | $0.00603 |
| Haiku 4.5 | $0.00006 | $0.00301 |
Grade A, and why
story-implementation-planner 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Story Implementation Planner
Own the Implementation Plan artifact. Turn an implementation-ready story and
repo evidence into an executable plan for a named or described executor without
clarifying the story, scouting the repository, assembling a packet, or editing
code.
Activation Contract
Use this skill only when all of these are true:
- the requested output is an implementation plan;
- the input is one materialized active Story Card, not a Split Story Set, with
Artifact Type: Story Card,Status: Ready, observable acceptance criteria, and a settled implementation boundary; - Repo Context contains enough evidence to locate the existing implementation, validation surface, and any convention needed for proposed files;
- every planning-critical external claim, when present, has current and
applicable primary-source support in Repo Context
External Evidence; and - executor constraints are known or can be stated conservatively without changing the required behavior or safety policy.
Use story-to-plan-orchestrator when the request spans clarification, scouting,
planning, packet assembly, readiness validation, or resumption. Use
story-clarifier for unresolved product behavior and story-repo-scout for
missing, weak, or stale repository evidence. Do not perform those stages here.
A ready Split Story Set still requires slice selection and materialization by
the orchestrator before it becomes valid planning input.
If this skill is invoked with inadequate inputs, return the supported portions of the artifact with a non-ready status and route the missing work to its owner. Do not fill gaps by guessing.
Status Contract
Every output starts with:
## Implementation Plan
Artifact Type: Implementation Plan
Status: Ready | Needs Input | Blocked
Reason: None | <concise readiness reason>
Use the statuses operationally:
Ready: the plan is executable as written and has no unresolved blocking input; writeReason: None.Needs Input: a specific answer, upstream revision, or re-scout can make the plan executable. Name each missing input, its owner, and the next action; do not write unsupported downstream steps.Blocked: a hard dependency or constraint prevents an honest plan and the required input cannot currently be obtained through the preparation workflow. Name the evidence, unblock condition, and safe stopping point.
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 Changed · +10 lines 40b93e8139b6
- 1mo ago First seen · 298 lines · 65 tokens per session scan A a95d5f062ec2
story-implementation-planner is a skill published in the GitHub repository n-n-code/n-n-code-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 3,015 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-08-31.
Other skills, from other repositories
astro-dso-doc
Bootstraps a deep-sky object (DSO) astrophotography project from raw acquisition frames (own rig, not a smart telescope), AND generates a complete, polished HTML documentation page, a processing checklist, an AstroBin post JSON, a PixInsight process icon set (XPSM), and a ready-to-paste PixInsight project Description…
logo-design
Professional logo and brand-mark design, from brief to production files. Guides discovery and the design brief, concept generation, choosing a mark type (wordmark, monogram, letterform, pictorial, abstract, emblem, mascot, combination), building clean geometric SVG logos, optical refinement, colour and typography…
llm-council
Run any question, idea, or decision through a council of 5 AI advisors who independently analyze it, peer-review each other anonymously, and synthesize a final verdict. Based on Karpathy's LLM Council methodology. MANDATORY TRIGGERS: 'council this', 'run the council', 'war room this', 'pressure-test this'…
document-code
Apply Google Style documentation standards to Python, Go, TypeScript, and Terraform code. Use when writing or reviewing code that needs docstrings/comments/JSDoc, when asked to "document this code", "add docstrings", "follow Google Style", or when improving code documentation quality. Supports Python docstrings, Go…
work-on-ticket
Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.
datadog
Use this skill when you need to search Datadog logs, query metrics, tail logs in real-time, trace distributed requests, investigate errors, compare time periods, find log patterns, check service health, or export observability data.