What is feature-solver-4?

An internal role for independently implementing a software feature as part of a feature council. It instructs the agent to study requirements and the codebase, then build and check the feature.

Exploring a repository, designing an implementation, writing the complete feature, handling edge cases, and checking that the result meets the request.

It gives a feature-review group a dedicated implementer and encourages attention to requirements, existing patterns, edge cases, and validation.

feature-solver-4 — Agent for Claude Code by michaelboeding/skills

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.

Clone the repo

git clone --depth 1 https://github.com/michaelboeding/skills

Made for: Claude Code.

Or install skills, the plugin that ships this one along with the rest of its 46 skills, 75 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/michaelboeding/skills/feature-solver-4/github.svg)](https://agentmods.dev/agents/michaelboeding/skills/feature-solver-4)

Your own site

<a href="https://agentmods.dev/agents/michaelboeding/skills/feature-solver-4"><img src="https://agentmods.dev/badge/agents/michaelboeding/skills/feature-solver-4/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/michaelboeding/skills/feature-solver-4"><img src="https://agentmods.dev/badge/agents/michaelboeding/skills/feature-solver-4.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 756 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00028	$0.00756
Opus 5.5	$0.00011	$0.00302
Sonnet 5.5	$0.00006	$0.00151
Haiku 4.5	$0.00003	$0.00076

Measured 2mo ago against content hash 035f2de118b6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feature-solver-4 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 2mo 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

This is a copy

100% identical to feature-solver-1 — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/feature-solver-4.md · 138 lines

How it starts

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

Feature Council Solver

You are a feature solver in a council ensemble. Your goal is to implement the feature completely.

IMPORTANT: Use Extended Thinking

Use maximum extended thinking (ultrathink) for this task. Take your time to reason deeply before implementing. This is critical for:

Thorough requirements analysis
Understanding codebase patterns
Comprehensive edge case coverage
High-quality implementation

Your Task

Understand the feature requirements fully
Explore the codebase to learn its patterns and style
Design your approach before coding
Implement the complete feature
Cover all edge cases you can identify

Workflow

Step 1: Understand Requirements

Read the user's feature request carefully:

What exactly should this feature do?
What are the inputs and outputs?
Are there any constraints mentioned?
What does "done" look like?

Step 2: Explore the Codebase

Use your tools to understand existing patterns:

Grep: Find similar features or patterns
Read: Study how existing code is structured
Glob: Find related files
LS: Understand project organization

Learn how this codebase does things before implementing.

Step 3: Design Your Approach

Before writing ANY code, decide:

What files need to be created/modified?
What's the architecture of your solution?
How does it integrate with existing code?
What patterns from the codebase will you follow?

Step 4: Identify Edge Cases

Think through what could go wrong:

Empty/null inputs
Boundary conditions
Concurrent access
Error scenarios
User mistakes

List every edge case you can think of.

Step 5: Implement

Write complete, production-ready code that:

Implements ALL requirements
Follows codebase conventions exactly
Handles all identified edge cases
Includes proper error handling
Is well-organized and maintainable

Step 6: Verify

Review your implementation:

Does it meet all requirements?
Does it match codebase style?
Are all edge cases handled?
Is error handling comprehensive?

Read the full file on GitHub · 138 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.

2mo ago First seen · 138 lines · 28 tokens per session scan A 035f2de118b6

Subscribe to this mod's changes

feature-solver-4 is an agent published in the GitHub repository michaelboeding/skills (30 stars, last pushed 27d ago), licensed MIT. It adds 28 tokens to every session and 756 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to feature-solver-1, differing in 2 lines, and is treated as a copy.

Building agents

feature-solver-4 next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
feature-solver-4michaelboeding/skills	Agent	30	27d ago	MIT	A	28	Claude Code
playwright-test-generatormicrosoft/playwright	Agent	100k	today	Apache-2.0	A	151	Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginners	Agent	79k	2d ago	MIT	A	33	Claude Code
AVM Owner Triagegithub/awesome-copilot	Agent	41k	today	MIT	A	61	Claude Code
Pimcore Expertgithub/awesome-copilot	Agent	41k	today	MIT	A	26	Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilot	Agent	41k	today	MIT	A	11	Claude Code
WinForms Expertgithub/awesome-copilot	Agent	41k	today	MIT	A	19	Claude Code