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 skills/jamkris/everything-gemini-code/claude-devfleetnpx skills add Jamkris/everything-gemini-code --skill claude-devfleetgit clone --depth 1 https://github.com/Jamkris/everything-gemini-codeWrote 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/skills/jamkris/everything-gemini-code/claude-devfleet)<a href="https://agentmods.dev/skills/jamkris/everything-gemini-code/claude-devfleet"><img src="https://agentmods.dev/badge/skills/jamkris/everything-gemini-code/claude-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.1 | $0.00036 | $0.01381 |
| Opus 5 | $0.00018 | $0.00691 |
| Sonnet 5 | $0.00007 | $0.00276 |
| Haiku 4.5 | $0.00004 | $0.00138 |
Grade A, and why
gemini-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 2d 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.
This is a copy
91% identical to claude-devfleet — 45 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gemini DevFleet Multi-Agent Orchestration
When to Use
Use this skill when you need to dispatch multiple Gemini CLI agents to work on coding tasks in parallel. Each agent runs in an isolated git worktree with full tooling.
Requires a running Gemini DevFleet instance connected via MCP:
gemini mcp add devfleet --transport http http://localhost:18801/mcp
How It Works
User → "Build a REST API with auth and tests"
↓
plan_project(prompt) → project_id + mission DAG
↓
Show plan to user → get approval
↓
dispatch_mission(M1) → Agent 1 spawns in worktree
↓
M1 completes → auto-merge → auto-dispatch M2 (depends_on M1)
↓
M2 completes → auto-merge
↓
get_report(M2) → files_changed, what_done, errors, next_steps
↓
Report back to user
Tools
| Tool | Purpose |
|---|---|
plan_project(prompt) |
AI breaks a description into a project with chained missions |
create_project(name, path?, description?) |
Create a project manually, returns project_id |
create_mission(project_id, title, prompt, depends_on?, auto_dispatch?) |
Add a mission. depends_on is a list of mission ID strings (e.g., ["abc-123"]). Set auto_dispatch=true to auto-start when deps are met. |
dispatch_mission(mission_id, model?, max_turns?) |
Start an agent on a mission |
cancel_mission(mission_id) |
Stop a running agent |
wait_for_mission(mission_id, timeout_seconds?) |
Block until a mission completes (see note below) |
get_mission_status(mission_id) |
Check mission progress without blocking |
get_report(mission_id) |
Read structured report (files changed, tested, errors, next steps) |
get_dashboard() |
System overview: running agents, stats, recent activity |
list_projects() |
Browse all projects |
list_missions(project_id, status?) |
List missions in a project |
Note on
wait_for_mission: This blocks the conversation for up totimeout_seconds(default 600). For long-running missions, prefer polling withget_mission_statusevery 30–60 seconds instead, so the user sees progress updates.
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.
- 2d ago First seen · 104 lines · 36 tokens per session scan A e6cde7a2e7b6
gemini-devfleet is a skill published in the GitHub repository Jamkris/everything-gemini-code (87 stars, last pushed 3mo ago), licensed MIT. It adds 36 tokens to every session and 1,381 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to claude-devfleet, differing in 45 lines, and is treated as a copy.
Other skills, from other repositories
redteam
Expertise in offensive security research, vulnerability analysis, CMS-focused application testing, and red team operations.
redteam-cms
Focused methodology for authorized CMS fingerprinting, component inventory, misconfiguration review, and vulnerability validation.
redteam-exploit-validation
Focused workflow for validating exploitability safely and turning candidate issues into reproducible, bounded proof.
redteam-recon
Focused reconnaissance workflow for authorized security assessments, bug bounty triage, lab targets, and CTF infrastructure.
redteam-reporting
Focused reporting workflow for converting verified red-team work into clear, reproducible assessment artifacts.
redteam-source-audit
Focused source-code security review workflow for web applications, CMS extensions, APIs, and supporting services.