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.
git clone --depth 1 https://github.com/oxygen-fragment/claude-modularWrote 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/commands/oxygen-fragment/claude-modular/create-feature)<a href="https://agentmods.dev/commands/oxygen-fragment/claude-modular/create-feature"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/create-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.
<a href="https://agentmods.dev/commands/oxygen-fragment/claude-modular/create-feature"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/create-feature.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.00000 | $0.00606 |
| Opus 5.5 | $0.00000 | $0.00242 |
| Sonnet 5.5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
create-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 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.
What it actually says
Create Feature Command
2. **Branch Management**
- Create feature branch: `feat/[feature-name]`
- Set up branch protection if needed
- Link to issue tracker (Linear, GitHub Issues)
3. **Core Implementation**
- Create main feature files following project conventions
- Implement core functionality with proper error handling
- Add input validation and security checks
- Follow established patterns and style guides
4. **Test Implementation**
- Generate unit tests for all new functions
- Create integration tests for feature workflows
- Add end-to-end tests for user-facing features
- Ensure minimum coverage thresholds are met
5. **Documentation**
- Update API documentation if applicable
- Add inline code documentation
- Create user-facing documentation
- Update changelog and migration guides
6. **Quality Assurance**
- Run linting and formatting tools
- Execute full test suite
- Perform security scanning
- Validate performance requirements
# Expected structure created:
# - feat/user-authentication branch
# - src/auth/authentication.{js,ts,py,go}
# - tests/auth/authentication.test.{js,ts,py,go}
# - docs/auth/authentication.md
# - Updated API documentation
```
```bash
# With additional options
/project:create-feature payment-processing --type=service --framework=express
# Creates service-specific structure:
# - services/payment/
# - middleware/payment-validation.js
# - routes/payment.js
# - tests/payment/
```
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 · 0 tokens per session scan A 0e2285029588
create-feature is a command published in the GitHub repository oxygen-fragment/claude-modular (285 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 606 tokens. 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 commands, from other repositories
check
Run project checks and fix any errors without committing.
act
Follow RED-GREEN-REFACTOR cycle approach for test-driven development.
compliance-check
Ejecuta todas las verificaciones de compliance de reglas.
implement
Execute all implementation tasks from tasks.md with test-driven development, parallel batching, and atomic commits.
git-workflow
Run review, tests, and commit steps, then prepare a pull request.
check-fix
Execute quality gates, fix any issues found, and create a single high-quality Conventional Commit summarizing all changes made.