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 agentmods add skills/undeadlist/claude-code-agents/new-featurenpx skills add undeadlist/claude-code-agents --skill new-featuregit clone --depth 1 https://github.com/undeadlist/claude-code-agentsWrote 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/undeadlist/claude-code-agents/new-feature)<a href="https://agentmods.dev/skills/undeadlist/claude-code-agents/new-feature"><img src="https://agentmods.dev/badge/skills/undeadlist/claude-code-agents/new-feature.svg" alt="Measured on agentmods" 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 | $0.00014 | $0.00269 |
| Opus 5 | $0.00007 | $0.00134 |
| Sonnet 5 | $0.00003 | $0.00054 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
new-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 4d 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.
What it actually says
New Feature Workflow
Build features using test-driven development. Provide the feature specification when invoking.
Execution (Sequential)
Step 1: Write Tests
Spawn test-writer with the feature requirements:
- Analyze feature specification
- Write failing tests first
- Cover happy path + edge cases
Step 2: Implement Feature
Spawn code-fixer with the feature requirements and test files:
- Implement feature following existing patterns
- Make all new tests pass
Step 3: Verify
Spawn test-runner:
- Run all tests (new + existing)
- Verify no regressions
Step 4: Browser QA (if UI feature)
Spawn browser-qa-agent:
- Navigate to the new feature
- Test interactions
- Check for console errors
Usage
Provide feature requirements when invoking:
/new-feature
Feature: User profile update endpoint
- PUT /api/users/:id
- Allow updating: name, email, avatar
- Require authentication
- Validate email format
- Return updated user
Skip browser-qa for
- Pure API features (no UI)
- Library/utility code
- Database migrations
- Background jobs
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.
- 4d ago First seen · 53 lines · 14 tokens per session scan A c514e7abdd97
new-feature is a skill published in the GitHub repository undeadlist/claude-code-agents (147 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 269 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-30.
Other skills, from other repositories
tdd
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
test-first-bugs
Enforces a test-driven bug-fixing workflow. Use when a user reports a bug, failing code, an error, or asks to fix something.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.
white-box-red-testing
Find bugs by writing tests that should pass but don't. Invoke manually on user-chosen scope (commits, files, or coverage threshold). Outputs red tests with structured rationale. Use when user asks to "stress-test", "find bugs in", "attack", or "break" code.
tdd
Test-driven development (TDD) process used when writing code. Use whenever you are adding any new code, unless the user explicitly asks to skip TDD or the code is exploratory/spike.
go-rig
Use this skill when building, reviewing, or refactoring Go code that must follow strict design discipline — ATDD/TDD workflow, explicit dependency injection, package-boundary discipline, and structured code review. Complements CLAUDE.md by focusing on process and design judgment rather than version-specific Go…