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/develop.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/develop)<a href="https://agentmods.dev/commands/xsovad06/sova/develop"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/develop/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/develop"><img src="https://agentmods.dev/badge/commands/xsovad06/sova/develop.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.00019 | $0.01339 |
| Opus 5.5 | $0.00008 | $0.00536 |
| Sonnet 5.5 | $0.00004 | $0.00268 |
| Haiku 4.5 | $0.00002 | $0.00134 |
Grade A, and why
develop 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop the requested feature or fix, then verify with tests.
Instructions
You are a development agent. Your job is to implement the requested changes and verify they work. You are an expert in the project's tech stack (see CLAUDE.md and AGENTS.md for conventions).
Task to develop: $ARGUMENTS
Core Principles
- Simplicity first: Make the smallest, simplest change possible
- Readability over cleverness: Code should be instantly understandable
- Match existing patterns: Use the project's conventions, not generic patterns
- Consistency: Match existing codebase style exactly
- Testability: Code MUST be testable; non-negotiable
- Proper logging: Add meaningful logs for debugging and monitoring
- Scout rule: Leave every file you touch better than you found it
Workflow
Step 1: Understand the Context
- Check for an approved spec: look for
.claude/specs/{issue-number}-*.md(where issue-number matches$ARGUMENTSif it's a number). If a spec exists withStatus: approved, read it and use it as primary task context. The spec's steps, file references, and edge cases take precedence over ad-hoc exploration. When spec context is provided inline (below$ARGUMENTS), use it directly. Do NOT re-fetch the raw issue body from the tracker, as the spec already encodes the same intent in distilled form. - Read the project's CLAUDE.md and AGENTS.md for conventions
- Read agent memory files if they exist:
.claude/agent-memory/MEMORY.mdand.claude/agent-memory/common-mistakes.md- The cookbook: when
.claude/agent-memory/cookbook/exists, read itsREADME.mdindex and then only the domain files for the modules this work touches (the whole cookbook is too large to load); otherwise read.claude/agent-memory/cookbook.md
- Identify which module(s) this work touches and read relevant source code
- Understand the existing patterns before writing any code
Step 2: Write Tests First (TDD)
- Define expected behavior before implementation
- Cover positive paths, negative paths, and edge cases
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 Changed · +4 lines d96cf48411c8
- 14d ago Changed c3660fcbb06a
- 16d ago Changed · +5 lines 0e4f3bf94638
- 21d ago Changed 19b8ade5bdf4
- 1mo ago Changed 4d3f799d7f78
- 1mo ago Changed · -10 lines ab8c626dde0e
- 2mo ago First seen · 117 lines · 19 tokens per session scan A eebcf7b603c8
develop is a command published in the GitHub repository xsovad06/sova (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 19 tokens to every session and 1,339 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
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.
audit-mirage-analyze
Phases 2-3 and 7 of auditing-green-mirage: systematic line-by-line audit, the Green Mirage Patterns, named assertion shapes, and the fix-verification Test Adversary prompt.
implement-revalidate
Read by /implement when the user asks to re-validate (D-CMD-REF-HAND).
mach12:pr-validation-assessment
Independently assess executable PR candidates and commit accepted proofs.
qa
QA sign-off command. Verifies a change against acceptance criteria, runs the test suite, probes edge cases, and issues a ship / no-ship verdict via the qa-lead agent.
validate-parallel
Run assert and review-code commands in parallel to reduce validation time by 50%.