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.
npx agentmods add commands/nmime/motiv-buy/developmentgit clone --depth 1 https://github.com/nmime/motiv-buyWrote 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/nmime/motiv-buy/development)<a href="https://agentmods.dev/commands/nmime/motiv-buy/development"><img src="https://agentmods.dev/badge/commands/nmime/motiv-buy/development.svg" alt="Measured on agentmods" 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.00529 |
| Opus 5 | $0.00000 | $0.00264 |
| Sonnet 5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
development 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 today.
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.
This is a copy
100% identical to development — 116 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Swarm Strategy
Purpose
Coordinated development through specialized agent teams.
Activation
Using MCP Tools
// Initialize development swarm
mcp__claude -
flow__swarm_init({
topology: 'hierarchical',
maxAgents: 8,
strategy: 'balanced',
});
// Orchestrate development task
mcp__claude -
flow__task_orchestrate({
task: 'build feature X',
strategy: 'parallel',
priority: 'high',
});
Using CLI (Fallback)
npx claude-flow swarm "build feature X" --strategy development
Agent Roles
Agent Spawning with MCP
// Spawn development agents
mcp__claude -
flow__agent_spawn({
type: 'architect',
name: 'System Designer',
capabilities: ['system-design', 'api-design'],
});
mcp__claude -
flow__agent_spawn({
type: 'coder',
name: 'Frontend Developer',
capabilities: ['react', 'typescript', 'ui'],
});
mcp__claude -
flow__agent_spawn({
type: 'coder',
name: 'Backend Developer',
capabilities: ['nodejs', 'api', 'database'],
});
mcp__claude -
flow__agent_spawn({
type: 'specialist',
name: 'Database Expert',
capabilities: ['sql', 'nosql', 'optimization'],
});
mcp__claude -
flow__agent_spawn({
type: 'tester',
name: 'Integration Tester',
capabilities: ['integration', 'e2e', 'api-testing'],
});
Best Practices
- Use hierarchical mode for large projects
- Enable parallel execution
- Implement continuous testing
- Monitor swarm health regularly
Status Monitoring
// Check swarm status
mcp__claude -
flow__swarm_status({
swarmId: 'development-swarm',
});
// Monitor agent performance
mcp__claude -
flow__agent_metrics({
agentId: 'architect-001',
});
// Real-time monitoring
mcp__claude -
flow__swarm_monitor({
swarmId: 'development-swarm',
interval: 5000,
});
Error Handling
// Enable fault tolerance
mcp__claude -
flow__daa_fault_tolerance({
agentId: 'all',
strategy: 'auto-recovery',
});
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.
- today First seen · 115 lines · 0 tokens per session scan A 59f2dfb628d9
development is a command published in the GitHub repository nmime/motiv-buy (0 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 529 tokens. A static security scan graded it A with 0 findings. It is 100% identical to development, differing in 116 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.