Borrowing it
Nothing to install: this file belongs to janekbaraniewski/openusage. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/janekbaraniewski/openusage/main/.claude/commands/develop-feature.mdgit clone --depth 1 https://github.com/janekbaraniewski/openusageWrote 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/janekbaraniewski/openusage/develop-feature)<a href="https://agentmods.dev/commands/janekbaraniewski/openusage/develop-feature"><img src="https://agentmods.dev/badge/commands/janekbaraniewski/openusage/develop-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/janekbaraniewski/openusage/develop-feature"><img src="https://agentmods.dev/badge/commands/janekbaraniewski/openusage/develop-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.00248 |
| Opus 5.5 | $0.00000 | $0.00099 |
| Sonnet 5.5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
develop-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
Develop the feature "$ARGUMENTS" end-to-end — from design to pull request.
Read and follow the full skill specification in docs/skills/develop-feature/SKILL.md.
This skill orchestrates the full development lifecycle:
-
Phase 0 — Intake: Check for existing design doc. Ask: full lifecycle or specific phase?
-
Phase 1 — Design (
/design-feature): Design the feature, produce design doc with tasks. -
Phase 2 — Review (
/review-design): Validate design against codebase, fix discrepancies. -
Phase 3 — Implement (
/implement-feature): Execute tasks with tests, parallel where possible. -
Phase 4 — Validate (
/validate-feature): Build, test, design compliance, code quality checks. -
Phase 5 — Iterate (
/iterate-feature): Fix issues from validation (loops until clean or user decides). -
Phase 6 — Finalize (
/finalize-feature): Create branch, commit, open PR. -
Phase 7 — Summary: Report full lifecycle results.
Each phase pauses for user confirmation before proceeding to the next.
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 · 24 lines · 0 tokens per session scan A 6ba23d1f85f6
develop-feature is a command published in the GitHub repository janekbaraniewski/openusage (235 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 248 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
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
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.
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.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.