Feature Plan

Feature Plan is a skill for Claude Code, Codex from onmyway133/claude-code-plugins. It costs 14 tokens per session (692 once invoked), scanned A, original, MIT.

A spaced-review command for revising knowledge recorded in a repository’s AGENTS.md file. Spaced review means revisiting material at planned intervals to improve recall.

In plain words
What is it for?
Use it to run review questions, identify missing knowledge, and update the repository’s review records, gaps, and progress tracker.
Why use it?
It directs attention to overdue topics and known gaps instead of relying on unstructured rereading.

Skill for Claude CodeCodex

Part of the super plugin — 6 skills, 5 commands, 6 agents, 4 MCP servers shipped together

Install

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.

agentmods
npx agentmods add skills/onmyway133/claude-code-plugins/feature-plan
Any agent
npx skills add onmyway133/claude-code-plugins --skill feature-plan
Clone the repo
git clone --depth 1 https://github.com/onmyway133/claude-code-plugins

Made for: Claude Code, Codex.

Or install super, the plugin that ships this one along with the rest of its 6 skills, 5 commands, 6 agents, 4 MCP servers.

Wrote 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.

agentmods badge for Feature Plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/onmyway133/claude-code-plugins/feature-plan.svg)](https://agentmods.dev/skills/onmyway133/claude-code-plugins/feature-plan)
Your own site
<a href="https://agentmods.dev/skills/onmyway133/claude-code-plugins/feature-plan"><img src="https://agentmods.dev/badge/skills/onmyway133/claude-code-plugins/feature-plan.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 692 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00692
Opus 5 $0.00007 $0.00346
Sonnet 5 $0.00003 $0.00138
Haiku 4.5 $0.00001 $0.00069

Measured 3d ago against content hash 029ef829208d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Feature Plan 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

plugins/super/skills/feature-plan/SKILL.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Feature Plan

When asked to plan a new feature, create a structured implementation blueprint.

Planning Process

Step 1: Understand Requirements

Before planning, clarify:

  • What problem does this feature solve?
  • Who are the users affected?
  • What's the expected behavior?
  • Are there edge cases or constraints?

Ask clarifying questions if requirements are ambiguous.

Step 2: Assess Current State

Explore the codebase to understand:

  • Existing patterns and architecture
  • Related features or components
  • Reusable code that can be leveraged
  • Potential conflicts or dependencies

Step 3: Design the Solution

Create a plan covering:

Architecture Overview
[User Action]
     ↓
[View Layer] ← What UI components
     ↓
[ViewModel/Logic] ← Business rules
     ↓
[Data Layer] ← Storage, network, etc.
Component Breakdown

For each component:

  • Purpose: What it does
  • Location: Where it lives in the codebase
  • Dependencies: What it needs
  • Interface: Public API it exposes
Data Flow

Describe how data moves:

  • User inputs and actions
  • State transformations
  • Persistence points
  • Output/display

Step 4: Identify Files to Modify

Create a concrete list:

File Action Changes
path/to/file Create New view model
path/to/existing Modify Add new method

Step 5: Define Implementation Sequence

Order tasks by dependencies:

1. [ ] Data models (no dependencies)
2. [ ] Repository/Service layer (depends on models)
3. [ ] ViewModel (depends on service)
4. [ ] Views (depends on view model)
5. [ ] Integration and testing

Step 6: Risk Assessment

Identify potential issues:

  • Breaking changes to existing features
  • Performance considerations
  • Security implications
  • Migration requirements

Plan Output Format

# Feature: [Name]

## Overview
Brief description of what we're building.

## Requirements
- [ ] Requirement 1
- [ ] Requirement 2

## Architecture

### Components
- **ComponentA**: Purpose and responsibility
- **ComponentB**: Purpose and responsibility

### Data Flow
[Diagram or description]

## Implementation Steps

### Phase 1: Foundation
- [ ] Task 1.1
- [ ] Task 1.2

### Phase 2: Core Logic
- [ ] Task 2.1

### Phase 3: UI
- [ ] Task 3.1

### Phase 4: Polish
- [ ] Testing
- [ ] Edge cases

## Files to Create/Modify
[Table of files]

## Risks and Considerations
- Risk 1: Mitigation strategy
- Risk 2: Mitigation strategy

## Open Questions
- Question needing user input

Read the full file on GitHub · 146 lines

Changes

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.

  1. 3d ago First seen · 146 lines · 14 tokens per session scan A 029ef829208d

Subscribe to this mod's changes

Feature Plan is a skill published in the GitHub repository onmyway133/claude-code-plugins (5 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 692 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.

Related

Other skills, from other repositories

design-taste-frontend

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

Leonxlnx/taste-skill · 61 tokens

image-to-code

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards…

Leonxlnx/taste-skill · 116 tokens

brandkit

Premium brand-kit image generation skill for creating high-end brand-guidelines boards, logo systems, identity decks, and visual-world presentations. Trained for minimalist, cinematic, editorial, dark-tech, luxury, cultural, security, gaming, developer-tool, and consumer-app brand systems. Optimized for intentional…

Leonxlnx/taste-skill · 89 tokens

minimalist-ui

Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.

Leonxlnx/taste-skill · 34 tokens

edgeone skill scanner

Scan any agent skill for security risks before you install or use it. Powered by Tencent Zhuque Lab A.I.G (AI-Infra-Guard). 100% local static analysis — no file contents or credentials leave your device. Compatible with CodeBuddy, Cursor, Windsurf, Claude Code, OpenClaw and more. Triggers on: 这个 skill 安全吗, skill 安全扫描…

Tencent/AI-Infra-Guard · 148 tokens

rubber-duck

Adversarial "rubber duck" review that turns explaining-out-loud into a hallucination check. The main session is the PRESENTER (it did the work — a design doc, investigation, or analysis — and holds the real reasoning) and reconstructs the topic to a LISTENER — a spawned subagent pinned to a DIFFERENT-vendor model that…

kirodotdev/KiroCrew · 161 tokens