A command that implements a feature from a specification or from the user's request, using GitHub and Git to manage the work. It can create an issue, make a branch, commit changes, push them, and open a pull request.

Use it to implement a specified feature, follow a project branch and commit convention, and submit the result for review.

It organizes the path from a written requirement to a reviewable code change and keeps the related issue connected.

How danielscholl/mvn-mcp-server configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to danielscholl/mvn-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/danielscholl/mvn-mcp-server/main/.claude/commands/add-feature.md

Clone the repo

git clone --depth 1 https://github.com/danielscholl/mvn-mcp-server

Made for: Claude Code.

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/commands/danielscholl/mvn-mcp-server/add-feature/github.svg)](https://agentmods.dev/commands/danielscholl/mvn-mcp-server/add-feature)

Your own site

<a href="https://agentmods.dev/commands/danielscholl/mvn-mcp-server/add-feature"><img src="https://agentmods.dev/badge/commands/danielscholl/mvn-mcp-server/add-feature/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/commands/danielscholl/mvn-mcp-server/add-feature"><img src="https://agentmods.dev/badge/commands/danielscholl/mvn-mcp-server/add-feature.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 471 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.00000	$0.00471
Opus 5	$0.00000	$0.00235
Sonnet 5	$0.00000	$0.00094
Haiku 4.5	$0.00000	$0.00047

Measured 9d ago against content hash 46a39725b207, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

add-feature 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 9d 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 add-feature — 0 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.

.claude/commands/add-feature.md · 61 lines

What it actually says

READ specs/$ARGUMENT

Before Starting:

gh: create a issue with the a short descriptive title.
GIT: checkout a branch and switch to it.

IMPLEMENT TOOL

Provide task updates to the issue if appropriate.

On Completion:

GIT: commit with a descriptive message.
GIT: push the branch to the remote repository.
gh: create a PR and link the issue.

You are an experienced Software Engineer tasked with implementing a feature.

First, let's review the feature arguments provided:

<feature_arguments> {{feature_ARGUMENTS}} </feature_arguments>

Begin by analyzing the feature and deciding if a spec exists.

If spec found READ spec.
If spec not found analyze feature and if vague ask for clarification.

GUIDANCE

Branch Naming:
- Use: agent/-
- Example: agent/42-fix-login-bug
Commit Message Format (Release Please):
- Use Conventional Commits style for Release Please automation
- Format: [optional scope]:
- Types that trigger releases:
  - feat: - New feature (minor version bump)
  - fix: - Bug fix (patch version bump)
  - feat!: or fix!: - Breaking change (major version bump)
- Types for maintenance (no version bump):
  - chore: - Maintenance tasks, dependency updates
  - docs: - Documentation changes
  - style: - Code formatting, no logic changes
  - refactor: - Code refactoring without new features
  - test: - Adding or updating tests
Merge Request (MR) Template:
- Description: Brief summary of the changes and why they were made
- Related Issues: List related issues (e.g., Closes #42, Relates to #15)
- Type of Change: Bug fix, New feature, Breaking change, or Documentation update
- Checklist: Code builds and passes tests, Documentation updated, Conventional commit format used, Reviewer assigned
- Additional Notes: Any extra context, screenshots, or deployment considerations

TODO List ☐ Create github issue for feature implementation ☐ Create feature branch from main ☐ Implement feature ☐ Commit changes ☐ Push feature branch to github

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.

9d ago First seen · 61 lines · 0 tokens per session scan A 46a39725b207

Subscribe to this mod's changes

add-feature is a command published in the GitHub repository danielscholl/mvn-mcp-server (0 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 471 tokens. A static security scan graded it A with 0 findings. It is 100% identical to add-feature, differing in 0 lines, and is treated as a copy.

Git and workflow

commit

A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.

echoVic/blade-code · 8 tokens

merge-conflict-analysis

You are analyzing merge conflicts for PR #${{ pr-number }}.

rjmurillo/ai-agents · 0 tokens

release-notes

Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.

OpenHands/extensions · 44 tokens

doctor

Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…

doncheli/don-cheli-sdd · 76 tokens

repo-audit

Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.

tractorjuice/arc-kit · 29 tokens

handoff

Export a Waybill Bundle by default, or import one when requested.

wardmos/waybill · 13 tokens

mvn-mcp-server: Command for Claude Code