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/kelp/agent-plugins/fleet-efficiencynpx skills add kelp/agent-plugins --skill fleet-efficiencygit clone --depth 1 https://github.com/kelp/agent-pluginsWhat 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.00059 | $0.00816 |
| Opus 5 | $0.00030 | $0.00408 |
| Sonnet 5 | $0.00012 | $0.00163 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
fleet-efficiency 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fleet Efficiency (context handoff, no duplicate reads)
When fanning out many agents (audits, migrations, multi-stage pipelines), the token bill lives in the subagents, not the main thread. Rules:
- Scout once, brief many. The orchestrator (or one scout agent) builds the repo map / file partition ONCE; every worker gets an explicit file list scoped to its task. Never let N agents each rediscover the repo.
- Shared preamble, identical bytes. Put the shared brief (architecture nutshell, conventions, rubric) as a byte-identical block at the TOP of every fleet prompt, per-agent task at the BOTTOM. Identical prefixes hit the prompt cache across the whole fleet; a reordered or reworded brief pays full price N times.
- Excerpt, don't point. Paste the ten relevant lines into the
prompt instead of "read CLAUDE.md first". A 9k-token doc read
by 150 agents is >1M tokens. If a project has a condensed
agent brief (e.g.
docs/agent-brief.md), paste that. - Hand artifacts forward. Every pipeline stage returns structured output (schema) carrying exactly what the next stage needs: code excerpts, file:line, diffs, commands run. A downstream agent re-reads source only when its JOB is to distrust the upstream one (adversarial verification); formatters, dedupers, and drafters should need zero file reads.
- Continue, don't respawn. For fix loops on the same artifact, SendMessage the original agent; its context is intact. Inside Workflow scripts (no continuation), include the prior diff and the reviewer's issue list in the fresh agent's prompt so it doesn't re-derive them.
- Keep fleet prompts byte-stable. No timestamps, run ids, or
other volatile values inside prompts; they bust Workflow
resume caching and cross-agent prompt caching. Pass volatile
values via
argsand reference them once. - Don't optimize away independence. Verifiers re-reading the code their finder cited is intentional redundancy; cut the briefing waste, not the adversarial checks.
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.
- yesterday First seen · 67 lines · 59 tokens per session scan A c4e955e512d6
fleet-efficiency is a skill published in the GitHub repository kelp/agent-plugins (2 stars, last pushed 8d ago), licensed MIT. It adds 59 tokens to every session and 816 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
shipping-artifacts
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded…
stakeholder-map
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.