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 alonf/specrew --skill carryover-plan-reviewgit clone --depth 1 https://github.com/alonf/specrewWrote 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/alonf/specrew/carryover-plan-review)<a href="https://agentmods.dev/skills/alonf/specrew/carryover-plan-review"><img src="https://agentmods.dev/badge/skills/alonf/specrew/carryover-plan-review.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 35 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00029 | $0.00562 |
| Opus 5 | $0.00015 | $0.00281 |
| Sonnet 5 | $0.00006 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
carryover-plan-review 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 5d 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
Context
Use this skill when a plan correction claims that previously missing carryover work has been restored. The reviewer must judge the live plan, not the effort story, and must prove that task-table changes, supporting narrative, and capacity math all agree.
Patterns
- Start with the live iteration plan. Confirm each named carryover appears as an explicit task row with requirement traceability.
- Check the same carryovers in the summary, acceptance/gate language, capacity revision, scope notes, and sequencing sections. Narrative-only carryovers are drift.
- Recompute the totals from the task table and compare them to the stated total and any staged split (for example Iter 1a / Iter 1b).
- Use decision inbox notes only as supporting evidence that the correction intent was recorded. They do not replace the live plan as the acceptance artifact.
- For “no unrelated drift” checks, inspect the tracked diff and verify changed sections are directly coupled to the carryover restoration and resulting math/text normalization.
Examples
specs\001-specrew-product\iterations\001\plan.md— live acceptance artifact for task presence, totals, and staged split..squad\decisions\inbox\picard-board-management-gap.mdand.squad\decisions\inbox\picard-worktree-execution-gap.md— intent records proving the two gap corrections were explicitly captured..squad\decisions\inbox\picard-carryover-correction.mdand.squad\decisions\inbox\data-carryover-capacity-revision.md— supporting notes for narrative and capacity normalization.
Anti-Patterns
- Accepting a correction because a decision note says the work was added without checking the live plan.
- Verifying task presence but skipping the capacity math or staged-split reconciliation.
- Treating unrelated new planning artifacts as part of the correction unless they are present in the tracked diff being reviewed.
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.
- 5d ago First seen · 38 lines · 29 tokens per session scan A 5ff7f66ea352
carryover-plan-review is a skill published in the GitHub repository alonf/specrew (54 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 562 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.