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 recursechat/agent-workflownpx agentmods add plugins/recursechat/agent-workflow/marketplacegit clone --depth 1 https://github.com/recursechat/agent-workflowGrade A, and why
recursechat-agent-workflow 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": "recursechat-agent-workflow",
"owner": {
"name": "recursechat"
},
"metadata": {
"description": "Claude Code plugins for agent workflows: Ghostty terminal notifications and permission auto-handling."
},
"plugins": [
{
"name": "ghostty-notifications",
"source": "./plugins/ghostty-notifications",
"description": "Ghostty terminal notifications for Claude Code events (bell, OSC 777). Notifies on permission prompts, idle, auth, and elicitation dialogs.",
"keywords": ["ghostty", "notifications", "bell", "terminal"]
},
{
"name": "yolo",
"source": "./plugins/yolo",
"description": "Auto-handle Claude Code permission requests. Route to Claude for security review, auto-approve everything, or turn off.",
"keywords": ["permissions", "security", "auto-approve", "hooks"]
}
]
}
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 · 24 lines scan A 653b63134237
recursechat-agent-workflow is a plugin published in the GitHub repository recursechat/agent-workflow (25 stars, last pushed 6mo ago), licensed Apache-2.0. 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-30.
Other plugins, from other repositories
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
nextjs
Official Claude Code plugin marketplace for Next.js, serving the skills that ship in the vercel/next.js repository.
claude-plugins-official
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.
knowledge-work-plugins
Plugin marketplace listing 97 plugins: noibu, productivity, enterprise-search, cowork-plugin-management, sales.
ecc
Plugin marketplace listing 1 plugin: ecc.
ecc
Harness-native ECC plugin for engineering teams - 68 agents, 286 skills, 94 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses.