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 6BNBN/FlowPilot --skill feature-devgit clone --depth 1 https://github.com/6BNBN/FlowPilotWrote 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/6bnbn/flowpilot/feature-dev)<a href="https://agentmods.dev/skills/6bnbn/flowpilot/feature-dev"><img src="https://agentmods.dev/badge/skills/6bnbn/flowpilot/feature-dev/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/6bnbn/flowpilot/feature-dev"><img src="https://agentmods.dev/badge/skills/6bnbn/flowpilot/feature-dev.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.00036 | $0.00709 |
| Opus 5.5 | $0.00014 | $0.00284 |
| Sonnet 5.5 | $0.00007 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
feature-dev 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex-Native Feature Development
Use this workflow when a feature request needs structured discovery before implementation. Keep update_plan current throughout, and use parallel explorer subagents for research only when their scopes are independent.
Source of truth
eferences/feature-dev-command.md
eferences/agent-prompts/code-architect.md
eferences/agent-prompts/code-explorer.md
eferences/agent-prompts/code-reviewer.md
Core Principles
- Ask clarifying questions early when behavior, edge cases, or scope are underspecified.
- Understand before acting by reading existing code patterns first.
- Read the files surfaced by subagents instead of relying on summaries alone.
- Prefer simple, maintainable designs over clever abstractions.
- Use update_plan to track progress and checkpoints.
Phase 1: Discovery
Goal: Understand what needs to be built.
Actions:
- Create a plan that covers discovery, design, implementation, and review.
- If the request is underspecified, ask concrete clarifying questions.
- Summarize your understanding and confirm it with the user.
Phase 2: Codebase Exploration
Goal: Understand relevant code and patterns.
Actions:
- Spawn 2-3 explorer subagents in parallel with disjoint research scopes.
- Ask each subagent to return the 5-10 most important files to read next.
- Read the returned files yourself and consolidate the patterns you found.
Phase 3: Clarifying Questions
Goal: Resolve ambiguities before design.
Actions:
- Review the request and the exploration findings.
- Identify missing details around scope, data flow, UX, errors, compatibility, and testing.
- Present the open questions clearly.
- Wait for user answers before designing architecture.
Phase 4: Architecture Design
Goal: Compare implementation approaches with trade-offs.
Actions:
- If the feature is large enough to justify it, spawn 2-3 explorer or worker subagents to propose different architectural approaches.
- Compare the approaches by change size, maintainability, risk, and implementation speed.
- Recommend one approach and explain why it fits best.
- Ask the user to confirm the direction.
What ships with it
4 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.
- 1mo ago First seen · 88 lines · 36 tokens per session scan A 72d816c963b8
feature-dev is a skill published in the GitHub repository 6BNBN/FlowPilot (136 stars, last pushed 7mo ago), licensed MIT. It adds 36 tokens to every session and 709 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
oma-voice
Generate or transcribe speech with Voicebox, or process existing audio locally. Use for narration, transcripts, timed speech, and loudness conversion; video editing uses oma-video.
oma-security
Scan application source, agent skills, and MCP components; run penetration tests against scoped web test deployments, validate findings, and configure scan gates. Use oma-qa for broad quality reviews and domain skills for remediation.
oma-architecture
Evaluate system boundaries and architectural tradeoffs. Use for architecture decisions, design reviews, and ADRs.
oma-brainstorm
Explore goals, constraints, and alternative approaches before choosing a design. Use when the user requests ideation or design exploration.
oma-explanation
Create an offline HTML explanation of a code change (diff, PR, branch) or of a topic, system, or question. Use when a visual walkthrough document is requested.
oma-observability
Design or troubleshoot telemetry, SLOs, and incident diagnostics. Route to the relevant signal, system boundary, or vendor guide.