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/loulanyue/awesome-claude-notes/devfleetgit clone --depth 1 https://github.com/loulanyue/awesome-claude-notesWrote 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/loulanyue/awesome-claude-notes/devfleet)<a href="https://agentmods.dev/commands/loulanyue/awesome-claude-notes/devfleet"><img src="https://agentmods.dev/badge/commands/loulanyue/awesome-claude-notes/devfleet.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 | $0.00033 | $0.00919 |
| Opus 5 | $0.00016 | $0.00460 |
| Sonnet 5 | $0.00007 | $0.00184 |
| Haiku 4.5 | $0.00003 | $0.00092 |
Grade A, and why
devfleet 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevFleet — Multi-Agent Orchestration
Orchestrate parallel Claude Code agents via Claude DevFleet. Each agent runs in an isolated git worktree with full tooling.
Requires the DevFleet MCP server: claude mcp add devfleet --transport http http://localhost:18801/mcp
Flow
User describes project
→ plan_project(prompt) → mission DAG with dependencies
→ Show plan, get approval
→ dispatch_mission(M1) → Agent spawns in worktree
→ M1 completes → auto-merge → M2 auto-dispatches (depends_on M1)
→ M2 completes → auto-merge
→ get_report(M2) → files_changed, what_done, errors, next_steps
→ Report summary to user
Workflow
- Plan the project from the user's description:
mcp__devfleet__plan_project(prompt="<user's description>")
This returns a project with chained missions. Show the user:
- Project name and ID
- Each mission: title, type, dependencies
- The dependency DAG (which missions block which)
-
Wait for user approval before dispatching. Show the plan clearly.
-
Dispatch the first mission (the one with empty
depends_on):
mcp__devfleet__dispatch_mission(mission_id="<first_mission_id>")
The remaining missions auto-dispatch as their dependencies complete (because plan_project creates them with auto_dispatch=true). When manually creating missions with create_mission, you must explicitly set auto_dispatch=true for this behavior.
- Monitor progress — check what's running:
mcp__devfleet__get_dashboard()
Or check a specific mission:
mcp__devfleet__get_mission_status(mission_id="<id>")
Prefer polling with get_mission_status over wait_for_mission for long-running missions, so the user sees progress updates.
- Read the report for each completed mission:
mcp__devfleet__get_report(mission_id="<mission_id>")
Call this for every mission that reached a terminal state. Reports contain: files_changed, what_done, what_open, what_tested, what_untested, next_steps, errors_encountered.
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 · 100 lines · 33 tokens per session scan A 679616afd681
devfleet is a command published in the GitHub repository loulanyue/awesome-claude-notes (270 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 919 once invoked, about $0.0002 per session on Opus 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-09-03.
Other commands, from other repositories
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
cost-tracker
Track session costs, understand token spend, and get optimization tips.
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
test
Run all PandaFilter verification steps in order. Stop and report on first failure. This is the required pre-commit gate.
dev-planner
Generate or update DEV-PLAN.md with phased development plan from Product-Spec.md.