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.
git clone --depth 1 https://github.com/natea/fitfinderWrote 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/natea/fitfinder/development)<a href="https://agentmods.dev/commands/natea/fitfinder/development"><img src="https://agentmods.dev/badge/commands/natea/fitfinder/development/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/natea/fitfinder/development"><img src="https://agentmods.dev/badge/commands/natea/fitfinder/development.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.00503 |
| Opus 5.5 | $0.00000 | $0.00201 |
| Sonnet 5.5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00050 |
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 2mo 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
Development Workflow Coordination
Purpose
Structure Claude Code's approach to complex development tasks for maximum efficiency.
Step-by-Step Coordination
1. Initialize Development Framework
Tool: mcp__claude-flow__swarm_init
Parameters: {"topology": "hierarchical", "maxAgents": 8, "strategy": "specialized"}
Creates hierarchical structure for organized, top-down development.
2. Define Development Perspectives
Tool: mcp__claude-flow__agent_spawn
Parameters: {
"type": "architect",
"name": "System Design",
"capabilities": ["api-design", "database-schema"]
}
Tool: mcp__claude-flow__agent_spawn
Parameters: {
"type": "coder",
"name": "Implementation Focus",
"capabilities": ["nodejs", "typescript", "express"]
}
Tool: mcp__claude-flow__agent_spawn
Parameters: {
"type": "tester",
"name": "Quality Assurance",
"capabilities": ["unit-testing", "integration-testing"]
}
Sets up architectural and implementation thinking patterns.
3. Coordinate Implementation
Tool: mcp__claude-flow__task_orchestrate
Parameters: {
"task": "Build REST API with authentication",
"strategy": "parallel",
"priority": "high",
"dependencies": ["database setup", "auth system"]
}
4. Monitor Progress
Tool: mcp__claude-flow__task_status
Parameters: {"taskId": "api-build-task-123"}
What Claude Code Actually Does
- Uses Write tool to create new files
- Uses Edit/MultiEdit tools for code modifications
- Uses Bash tool for testing and building
- Uses TodoWrite tool for task tracking
- Follows coordination patterns for systematic implementation
Remember: All code is written by Claude Code using its native tools!
CLI Usage
# Start development workflow via CLI
npx claude-flow workflow dev "REST API with auth"
# Create custom workflow
npx claude-flow workflow create --name "api-dev" --steps "design,implement,test,deploy"
# Execute saved workflow
npx claude-flow workflow execute api-dev
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.
- 2mo ago First seen · 78 lines · 0 tokens per session scan A 57ba83b3e97d
development is a command published in the GitHub repository natea/fitfinder (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 503 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-09-03.
development compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| developmentnatea/fitfinder | Command | 4 | 1y ago | MIT | A | 0 | Claude Code |
| initfcakyon/claude-codex-settings | Command | 1.2k | today | Apache-2.0 | A | 0 | Claude Code |
| http-serviceMadAppGang/magus | Command | 14 | yesterday | MIT | A | 27 | Claude Code |
| buildAzure/ai-gateway | Command | 5 | 10d ago | MIT | A | 0 | Claude Code |
| api-contract-reviewMozurok/fhorja.dev | Command | 10 | 28d ago | MIT | A | 64 | Claude Code |
| start-10-1minicoohei/ai-agent-camp | Command | 347 | 1mo ago | none | A | 2 | Claude Code |
| fastapimfmezger/ai_agent_dotfiles | Command | 7 | 3mo ago | MIT | A | 84 | Claude Code, Gemini CLI |