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 agentmods add skills/devstride/claude-plugin/insert-storynpx skills add devstride/claude-plugin --skill insert-storygit clone --depth 1 https://github.com/devstride/claude-pluginWhat 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 | $0.00027 | $0.03093 |
| Opus 5 | $0.00014 | $0.01546 |
| Sonnet 5 | $0.00005 | $0.00619 |
| Haiku 4.5 | $0.00003 | $0.00309 |
Grade A, and why
insert-story 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 yesterday.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Human output. Read ${CLAUDE_PLUGIN_ROOT}/skills/build-item/references/plain-language-output.md once per top-level run; composed skills reuse it. Apply it to every message.
Insert a NEW Story (the one-day leaf role — this org's Story type) into a live DevStride roadmap — spliced into the dependency chain and dated so the /devstride:build-item loop picks it up NEXT. Its POSITION in the sequence looks native to the plan; its DESCRIPTION stays an honest spec of the real work (see the IMPORTANT note below — this is a splice/date operation, not a fabricated history). This is also the canonical capture path that build-item step 6.5 and ultracode-build use to turn an untracked deferral or newly-found follow-up into tracked, dependency-ordered work.
Argument — free text describing the story, optionally prefixed/suffixed with a parent item number
(any grouping level of your org's hierarchy, e.g. this org's Module/Capability/Epic — as in
I20100 add rate limiting to webhook intake or just add rate limiting to webhook intake): $ARGUMENTS
IMPORTANT — the DevStride MCP targets PRODUCTION (api.devstride.com). Every create/update here is a real, user-visible change to the live plan.
IMPORTANT — this is a Gantt-grooming skill: it changes DevStride data only, never the repo. If the user also wants code changes, that's a separate /devstride:build-item run AFTER this item exists.
0. Resolve the parent and read the plan
- First, require enough to act on. If
$ARGUMENTScarries no real description of the work (just an item number, or an empty/vague invocation), STOP and ask the user what the story actually is before creating or splicing anything — do NOT invent one. - If
$ARGUMENTScontains an item number (I#####), that is the anchor —get_item(view:"full")it, and resolve the org's REAL container/leaf work type names viaget_work_type_hierarchyto classify it (never assume the literal Capability/Epic/Story names). If it's a top-level container (this org's Module), you'll need to find/create a housing container at the level below (step 2). If it's already a lower-level container (this org's Capability or Epic), it IS the direct parent. - If no item number is given, ask the user which parent item (any grouping level — this org: Module/Capability/Epic) this story belongs to — do NOT guess at a plan to insert into.
- Pull the full descendant tree under the resolved anchor with
search_items(hierarchy=[anchor], itemType=workitem, noisDonefilter, limit 200) to see the current shape: which children are containers and which are executable leaves (this org: Capabilities/Epics vs Stories/Defects), their lanes, and their dates. - For each candidate container in that tree, fetch its
blocked_by/blocksrelationships (get_item(view:"full", fields:["number","relationships"])) — for a big tree, fan this out with aWorkflow(chunks of ~10 items/agent) rather than serial reads.
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.
- yesterday First seen · 82 lines · 27 tokens per session scan A 5b1bb1d1cd8a
insert-story is a skill published in the GitHub repository devstride/claude-plugin (2 stars, last pushed 3d ago), licensed MIT. It adds 27 tokens to every session and 3,093 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…