develop

A development command that continues work on a product by following the newest plan in its sprints folder.

In plain words
What is it for?
Finding the latest sprint, reviewing the existing product code, implementing the next planned work, and marking finished roadmap items.
Why use it?
It gives the agent a defined place to find the current work plan and keeps the roadmap updated as features are completed.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/manavsehgal/vibesolver/develop
Clone the repo
git clone --depth 1 https://github.com/manavsehgal/vibesolver

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 47 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00047
Opus 5 $0.00000 $0.00023
Sonnet 5 $0.00000 $0.00009
Haiku 4.5 $0.00000 $0.00005

Measured yesterday against content hash 39f677727768, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

.claude/commands/develop.md · 2 lines

What it actually says

Read the sprints/ folder to identify the latest sprint. Review the product code generated so far. Continue developing the product based on the latest spring plan. If roadmap features were completed then mark them completed in specs/roadmap.md

Changes

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.

  1. yesterday First seen · 2 lines · 0 tokens per session scan A 39f677727768

Subscribe to this mod's changes

develop is a command published in the GitHub repository manavsehgal/vibesolver (5 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 47 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-31.