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/okisdev/claude-code-fusionWrote 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/okisdev/claude-code-fusion/devin)<a href="https://agentmods.dev/plugins/okisdev/claude-code-fusion/devin"><img src="https://agentmods.dev/badge/plugins/okisdev/claude-code-fusion/devin/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/okisdev/claude-code-fusion/devin"><img src="https://agentmods.dev/badge/plugins/okisdev/claude-code-fusion/devin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
devin 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 today.
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-plugin-manifest.json",
"name": "devin",
"displayName": "Devin Companion",
"version": "0.0.68",
"description": "Local Devin CLI delegation: multi family consults, SWE implementation in owned worktrees, review, resumable history, background jobs, and setup health checks.",
"author": {
"name": "Harry Yep"
},
"homepage": "https://github.com/okisdev/claude-code-fusion",
"repository": "https://github.com/okisdev/claude-code-fusion",
"license": "MIT",
"keywords": [
"devin",
"multi-model",
"delegation",
"code-review",
"orchestration"
]
}
What it installs
The manifest is a name and a version. 2 skills, 1 agent travel with it, and installing the plugin installs all of them — 102 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.
- today First seen · 21 lines scan A 739d81b40903
devin is a plugin published in the GitHub repository okisdev/claude-code-fusion (3 stars, last pushed today), 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-10-30.
Other plugins, from other repositories
swarm-pi-code-plugin
Portable Pi workflows with durable Host Assistance, discovery, review, and isolated implementation.
ibrahim-plugins marketplace
Official Claude Code plugins by Ibrahim — AI image generation, multi-agent orchestration, and more.
great-cto
You already have the agent. This is everything around it. greatcto runs Claude Code as a pipeline of 72 specialist agents — an independent model checks each stage before the next builds on it, spending caps refuse rather than warn, and three decisions stay yours: what gets built, how, and whether it ships.
asdlc
Agentic SDLC workflows: plan a spec or Jira ticket with a human approval gate, build it task by task, review PRs with a three-lens council, and run a pre-delivery quality check.
relay
Delegate work packets from a lead Claude Code session to executor sessions in their own iTerm tabs, with session reuse instead of always spawning fresh.
good-bad-ugly
The Good, the Bad and the Ugly — tiered multi-agent orchestration for Claude Code. The Good (brain) plans and verifies, the Bad (judgment executor) handles work needing taste, the Ugly (mechanical executor) does the grunt work — in parallel herdr panes with fenced scopes.