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 MichaelYcJo/SpecSeal --skill feature-plannergit clone --depth 1 https://github.com/MichaelYcJo/SpecSealWrote 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/michaelycjo/specseal/feature-planner)<a href="https://agentmods.dev/skills/michaelycjo/specseal/feature-planner"><img src="https://agentmods.dev/badge/skills/michaelycjo/specseal/feature-planner.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.00081 | $0.00568 |
| Opus 5 | $0.00041 | $0.00284 |
| Sonnet 5 | $0.00016 | $0.00114 |
| Haiku 4.5 | $0.00008 | $0.00057 |
Grade A, and why
feature-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 3d 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
feature-planner — write the scope down before it moves
Scope that lives in someone's head grows quietly, and nobody can point to when it did. Decomposing the work orders it; writing down what is not in it is what makes the boundary hold later.
Planning Steps
1. Requirements Clarification
- What exactly is being requested?
- What's explicitly NOT in scope?
- What are the acceptance criteria?
- Any constraints (performance, compatibility, timeline)?
2. Existing Code Analysis
- What related code already exists?
- What patterns does the project use?
- What can be reused/extended vs built new?
- What will break if we change X?
3. Implementation Plan
- Break into ordered tasks (dependencies mapped)
- Identify parallel vs sequential work
- Estimate which files change
- Flag risky parts that need extra care
4. Scope Lock
- List what's IN scope (explicit)
- List what's OUT of scope (explicit)
- Get user confirmation before starting
Rules
- No gold-plating: plan only what's requested
- Identify the MVP path first
- Flag unknowns early (don't discover them mid-implementation)
- If >10 files affected, suggest phased approach
Where the output goes
Into seal/specs/<work-item-id>/plan.md, as its Phases table — one row per phase,
with the Verified by and Status columns that table carries. There is
no separate task-list file and no separate root for one.
What that costs: a phase row holds an ordered slice, not a dependency graph, so the parallel markers in the format below do not survive into the file. They are for the conversation that produces the plan. Work finishing in one session needs no file at all.
Output Format
## Feature: [name]
**Scope**: [in] / **Not**: [out]
**Tasks** (in order):
1. [task] - [files affected]
2. [task] - [files affected]
↳ depends on #1
3. [task] - [files affected] (parallel with #2)
**Risks**: [what could go wrong]
**Questions**: [what needs user input]
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.
- 3d ago Changed · +4 lines da9308be357f
- 7d ago First seen · 73 lines · 81 tokens per session scan A 9eae02cf9b8a
feature-planner is a skill published in the GitHub repository MichaelYcJo/SpecSeal (1 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 568 once invoked, about $0.0004 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…