Borrowing it
Nothing to install: this file belongs to xsovad06/sova. 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/xsovad06/sova/main/.claude/commands/new-feature.mdgit clone --depth 1 https://github.com/xsovad06/sovaWrote 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/xsovad06/sova/new-feature)<a href="https://agentmods.dev/commands/xsovad06/sova/new-feature"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/new-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/xsovad06/sova/new-feature"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/new-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.00014 | $0.00574 |
| Opus 5.5 | $0.00006 | $0.00230 |
| Sonnet 5.5 | $0.00003 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00057 |
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 14d 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start New Feature
Set up a new feature branch and prepare for development.
Feature name/description: $ARGUMENTS
Workflow
1. Ensure Clean Starting Point
- Resolve the default branch:
BASE=$(gh repo view --json defaultBranchRef --jq .defaultBranchRef.name) - Fetch it:
git fetch origin "$BASE" - Ensure the current working tree is clean:
git status
2. Create Feature Branch
- Derive a branch name from the description (lowercase, hyphenated)
- Features:
feat/<name>(e.g.,feat/income-crud) - Fixes:
fix/<name>(e.g.,fix/currency-conversion) - Refactors:
refactor/<name>(e.g.,refactor/auth-flow)
- Features:
- If the project keeps active branches in worktrees (
.claude/worktrees/exists, or its rules say so), create the branch in a new worktree so the primary checkout stays on the base branch, then do all further work from that directory:BASE=$(gh repo view --json defaultBranchRef --jq .defaultBranchRef.name) git worktree add ".claude/worktrees/<issue-or-topic>" -b "<branch-name>" "origin/$BASE" - Otherwise, from a checkout on the base branch:
git pull origin "$BASE", thengit checkout -b <branch-name>
3. Review Context
- Read CLAUDE.md and AGENTS.md for project conventions
- Read agent memory files if they exist (
.claude/agent-memory/; for a split cookbook in.claude/agent-memory/cookbook/, read itsREADME.mdindex and only the relevant domain files) - Identify which existing modules/files will be affected
4. Plan
- Break the feature into concrete implementation tasks
- Create a TodoWrite list with the tasks
- Identify any dependencies or prerequisites
5. Report
Tell the user:
- Branch name created
- High-level implementation plan
- Which files/modules will be affected
- Any questions or ambiguities to resolve before starting
- Suggest running
/develop <description>to begin implementation
Cross-References
- Ready to implement? Run
/develop <description>or/develop-full <description> - Need to understand approaches first? Run
/develop-explain <description>
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.
- 14d ago Changed · +5 lines 8d79c4c6eb78
- 2mo ago First seen · 58 lines · 14 tokens per session scan A e1771b833f7a
new-feature is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 574 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
merge
Consolidate feature branch changes and create final PR to main. This completes the v5.0 feature branch workflow after all task PRs have been merged.
update
Check for and apply KARIMO updates from GitHub releases.
code-review
Review the current branch changes for bugs and style issues.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
end
End a work session - a settlement pass that reconciles uncommitted / unpushed work + session context into git, the tracker, and a session snapshot file. --session (aliases --snapshot, --pre-compact, --compact) skips settlement and only writes the shared snapshot, keeping the session going.
address-pr-feedback
Systematically address PR review comments. Fetches all threads, categorizes by status (acknowledged, silently fixed, unaddressed), and guides user through posting replies and implementing fixes with explicit approval.