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 Codoop/codoop-flownpx agentmods add plugins/codoop/codoop-flow/marketplacegit clone --depth 1 https://github.com/Codoop/codoop-flowGrade A, and why
codoop-flow 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.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-marketplace.json",
"name": "codoop-flow",
"description": "codoop-flow: in-session orchestration for an AI-coding ticket pipeline (build/verify/review/ship) with a deterministic guardrail CLI.",
"owner": {
"name": "Codoop",
"url": "https://github.com/Codoop"
},
"plugins": [
{
"name": "codoop-flow",
"version": "0.1.7-alpha.2",
"source": ".",
"description": "Drive codoop-flow tickets in-session: pick -> build -> verify -> review -> ship, plus project initialization, discovery, and ticket design.",
"homepage": "https://github.com/Codoop/codoop-flow",
"license": "MIT",
"keywords": ["skills", "agents", "pipeline", "tickets", "review", "ship", "worktree"]
}
]
}
What ships with it
1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 21 lines scan A af73b76f9dc6
codoop-flow is a plugin published in the GitHub repository Codoop/codoop-flow (5 stars, last pushed 8d 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
specialist-agent
Plugin marketplace listing 1 plugin: specialist-agent.
specialist-agent
Your AI development team. 36 agents and 32 skills for building, reviewing, debugging, and shipping production code. Supports Vue, React, Next.js, SvelteKit, Angular, Astro, and Nuxt.
avtr-antidote
Plugin marketplace listing 1 plugin: antidote.
antidote
Stop AI agents from patching symptoms. Forces structural root-cause fixes over symptom patching in any language or stack.
pdca-framework
TDD-disciplined AI code generation using Plan-Do-Check-Act methodology. Enforces architecture-first analysis, strict red-green-refactor, Socratic ACT retrospectives, and optional Beads task tracking integration.
m2ui
Metin2 UI code generator skill — create and modify client UI from screenshots, descriptions, or existing scripts.