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.
/plugin marketplace add CaptainMe-AI/lead-dev-osnpx agentmods add plugins/captainme-ai/lead-dev-os/marketplacegit clone --depth 1 https://github.com/CaptainMe-AI/lead-dev-osGrade A, and why
captainme-ai 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.
What it actually says
{
"name": "captainme-ai",
"owner": {
"name": "CaptainMe-AI",
"url": "https://github.com/CaptainMe-AI"
},
"metadata": {
"description": "CaptainMe-AI plugins for Claude Code — spec & context-driven development tools"
},
"plugins": [
{
"name": "lead-dev-os",
"source": "./lead-dev-os",
"description": "Spec & context-driven framework for Claude Code development. Structured skills for product planning, spec writing, task scoping, and context-aware implementation.",
"version": "1.0.0",
"author": {
"name": "CaptainMe-AI",
"url": "https://github.com/CaptainMe-AI"
},
"license": "MIT",
"homepage": "https://captainme-ai.github.io/lead-dev-os/",
"repository": "https://github.com/CaptainMe-AI/lead-dev-os",
"keywords": ["spec-driven", "context-aware", "planning", "implementation", "workflow"],
"category": "workflow"
}
]
}
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 · 28 lines scan A f4c69702b05a
captainme-ai is a plugin published in the GitHub repository CaptainMe-AI/lead-dev-os (2 stars, last pushed 12d 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
synapti-marketplace
Plugin marketplace listing 8 plugins: decipon, gh-workflow, context-ledger, flow, agent-capability-standard.
ai-first-org-design-kit
Fourteen opinionated skills that guide founders and leaders through designing, deploying, adopting, and evolving organizations where agents handle coordination and execution while humans own specification and judgment. Diagnose coordination overhead, encode organizational identity, write agent-ready specifications…
context-ledger
Structured product development methodology with traceable evidence, explicit decisions, and constrained spec generation. Forces auditability through semantic IDs, quality gates, and impact-aware updates.
decipon
NCI (Narrative Credibility Index) manipulation detection with integrated deep research fact-checking. Analyzes content for propaganda, disinformation, and manipulation patterns across 20 categories. Includes claim verification using deep research methodology.
sound
Code taste as installable rules. Probe a repo's stack, select only the rules its code shows a surface for (evidence-cited per rule), confirm, and scaffold a browsable .claude/sound/ rule map (surfaced by the sound:prime skill). Installed rules are user-owned; re-runs reconcile.
storytelling-web-marketplace
Create stunning, animation-rich exploratory visual web pages from text content.