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/fledgeling-co/fledgeling-pluginsWrote 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/plugins/fledgeling-co/fledgeling-plugins/flagship)<a href="https://agentmods.dev/plugins/fledgeling-co/fledgeling-plugins/flagship"><img src="https://agentmods.dev/badge/plugins/fledgeling-co/fledgeling-plugins/flagship/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/plugins/fledgeling-co/fledgeling-plugins/flagship"><img src="https://agentmods.dev/badge/plugins/fledgeling-co/fledgeling-plugins/flagship.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
flagship 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 5d 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
{
"name": "flagship",
"version": "1.7.3",
"description": "Conduct many concurrent Claude Code sessions as one portfolio — the layer above ship-armada:ship-armada, for when the work is already spread across a dozen live sessions rather than waiting in one repo's backlog. Builds a roster of every peer session, learns what each owns, and coordinates them over SendMessage: hands out a capped heavy-work token derived from harbourmaster's measured berths rather than an invented number, batches their accumulated decisions through the perch R1–R5 router so only the operator's own axes reach the operator, routes judgement to defer's lanes after probing which are actually reachable, and propagates each session's findings to the others — which is the real return, because nine sessions independently found one tool's bug in a single evening and none knew about the others. Starts new work as a workflow, a subagent, or a fresh Ghostty tab using recover-claude-code:recover-claude-code's hardened mechanism, so a session can carry its own fleet. Holds the map and no authority: a conducting session cannot command a peer, cannot close a peer's channel to its user, and cannot relay an authorisation — all three were refused by ten sessions in one night and all three refusals were right. Includes flagship:fleet-console to review and continue already-authorised Claude, Codex, Grok, Cursor and Muse work through verified native controls or permitted Ghostty computer use, preserving session ownership and delivery evidence.",
"category": "development"
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 384 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 5d ago Changed 12bfb23d0393
- 1mo ago Changed 4f2a2e123f36
- 1mo ago Changed 6421d09f949d
- 1mo ago First seen · 7 lines scan A 4a2d0f65c901
flagship is a plugin published in the GitHub repository fledgeling-co/fledgeling-plugins (2 stars, last pushed 4d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills own folder layout and templates; /obw:pm splits a spec into blocking tickets; /issue is a Claude Mod pane that lists a view of the project's dashboard, draws Mermaid as text diagrams, and can open a card in the browser through viz.…
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.
mission-control
SDLC management for Operations, Asgard, and CAMPPS: prepared issue drafts, live schema sync, board schemas, labels, project fields, metrics, and card validation.
feishu-calendar
Manage Feishu (Lark) calendar events — create, read, update, delete events and manage attendees via the Feishu Open Platform Calendar API v4.
gse
GSE-One — AI engineering companion for structured SDLC management. 24 commands, adaptive risk analysis, unified backlog, knowledge transfer, worktree isolation.