Borrowing it
Nothing to install: this file belongs to ccbud/CCBuddy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ccbud/CCBuddy/main/.agents/skills/feature-boundary-planner/SKILL.mdgit clone --depth 1 https://github.com/ccbud/CCBuddyWrote 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/ccbud/ccbuddy/feature-boundary-planner)<a href="https://agentmods.dev/skills/ccbud/ccbuddy/feature-boundary-planner"><img src="https://agentmods.dev/badge/skills/ccbud/ccbuddy/feature-boundary-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/ccbud/ccbuddy/feature-boundary-planner"><img src="https://agentmods.dev/badge/skills/ccbud/ccbuddy/feature-boundary-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.00050 | $0.01097 |
| Opus 5.5 | $0.00020 | $0.00439 |
| Sonnet 5 | $0.00010 | $0.00219 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
feature-boundary-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 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Boundary Planner
Trace the requested behavior through the current checkout. A feature belongs in the result only when current source or an explicit new requirement supports it. Verify referenced paths and symbols before using them; do not reconstruct removed functionality from historical catalogs.
Choose The Scope
- impact-only: inspect and report without changing code or product specs.
- planning: establish behavior and acceptance cases before implementation.
- implementation-handoff: turn confirmed decisions into a bounded implementation and validation plan.
Use the mode implied by the request. Clarify only unknown decisions that materially change the scope; do not ask the user to reconfirm facts already established in this task.
Find Current Evidence
- Search aliases and node IDs in ccbuddy-feature-graph.yaml for the user's terms. Read only matched nodes and their one-hop relationships, then verify the declared files, symbols and semantics against the current checkout. The graph is a curated seed index, not a complete feature inventory. Use source-discovery.md to fill gaps or start when there is no match. Read the relevant existing contracts and package scripts; read
DESIGN.mdfor UI work andCONTEXT.mdfor plugin-store work. - Locate the entrypoint with
rg --filesand focusedrg -nsearches. Trace direct callers withpnpm dep:refs <file>:<symbol>when the symbol is a TypeScript export. If an indexed codegraph tool is available, use it as additional evidence and verify its paths against the checkout. - Classify the change: presentation, option source, draft/default, validation, commit effect, persistence, or recovery.
- Trace each user surface separately through validation and the command that commits the change. Shared UI components do not establish shared state or side effects.
- Identify the authoritative owner, derived views, protocol boundary, persistence and failure behavior. Name the semantic reason for each upstream or downstream dependency; imports alone do not prove a product relationship.
- Inspect one meaningful semantic hop first, expanding only when an unresolved owner or caller requires it. Rank relationships as must-inspect, should-inspect, conditional, invariant-only, or evidence-only.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 69 lines · 50 tokens per session scan A 0e9c39feae1d
feature-boundary-planner is a skill published in the GitHub repository ccbud/CCBuddy (8 stars, last pushed yesterday), licensed Apache-2.0. It adds 50 tokens to every session and 1,097 once invoked, about $0.0002 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-25.
Other skills, from other repositories
kanban-video-orchestrator
Plan and run multi-agent video production pipelines.
sdlc-review
Review Kanban handoffs and route verified outcomes.
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
gh-issues
Use when creating, triaging, or commenting on GitHub issues for the Kilo VS Code extension or JetBrains plugin via gh. Covers issue templates, project board assignment, title conventions, and required gh scopes.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
spec-to-backlog
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When an agent needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements…