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 joris887/exosuitnpx agentmods add plugins/joris887/exosuit/exosuitgit clone --depth 1 https://github.com/joris887/exosuitGrade A, and why
exosuit 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{
"name": "exosuit",
"version": "5.0.0",
"description": "Suit up. Build anything. A full engineering organization for Claude Code \u2014 deep idea interrogation, TDD sprints, enforced quality gates. 43 skills, 8 agents, 13 hooks, path-scoped rules.",
"homepage": "https://github.com/joris887/exosuit",
"author": {
"name": "Joris Deumens",
"url": "https://github.com/joris887"
},
"license": "MIT",
"skills": "./.claude/skills/",
"agents": [
"./.claude/agents/architecture-reviewer.md",
"./.claude/agents/code-reviewer.md",
"./.claude/agents/codebase-explorer.md",
"./.claude/agents/integration-tester.md",
"./.claude/agents/performance-engineer.md",
"./.claude/agents/research-analyst.md",
"./.claude/agents/security-analyst.md",
"./.claude/agents/spec-reviewer.md"
],
"hooks": "./.claude/hooks/hooks.json",
"settings": {
"includeGitInstructions": false,
"attribution": {
"commit": "Co-Authored-By: Claude <[email protected]>"
},
"plansDirectory": "docs/plans",
"outputStyle": "${CLAUDE_PLUGIN_ROOT}/.claude/output-styles/framework.md",
"env": {
"EXOSUIT_PROJECT_PROFILE": "standard",
"EXOSUIT_EXPLAIN_MODE": "brief",
"EXOSUIT_STOP_MAX_ITERATIONS": "5"
},
"statusLine": {
"type": "command",
"command": "bash ${CLAUDE_PLUGIN_ROOT}/.claude/hooks/status-line.sh"
},
"spinnerVerbs": {
"mode": "append",
"verbs": [
"Discovering",
"Planning",
"Building",
"Testing",
"Reviewing",
"Shipping",
"Analyzing",
"Refactoring",
"Investigating"
]
},
"spinnerTipsOverride": {
"excludeDefault": false,
"tips": [
"Use /story-cycle for structured story delivery",
"Run /doctor to check framework health",
"Use /research for evidence-backed decisions",
"TDD first \u2014 write tests before implementation",
"Use /handoff before What ships with it
1 file beside plugin.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.
- 2d ago First seen · 69 lines scan A d7bc77b1e3c4
exosuit is a plugin published in the GitHub repository joris887/exosuit (4 stars, last pushed 13d 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
lane-stack
Solo PM conveyor for Claude Code: orchestrator agents, lane playbooks, onboard and resume commands.
lid-experimental
Experimental LID skills with opt-in installation and explicit lifecycle (promotion or retirement). Layers on top of linked-intent-dev and arrow-maintenance.
deep-dashboard
deep-dashboard. Harness layer for Claude Code & Codex: plan-first development, independent review, durable long-running orchestration, and knowledge capture — ten composable plugins.
deep-docs
deep-docs. Harness layer for Claude Code & Codex: plan-first development, independent review, durable long-running orchestration, and knowledge capture — ten composable plugins.
deep-evolve
deep-evolve. Harness layer for Claude Code & Codex: plan-first development, independent review, durable long-running orchestration, and knowledge capture — ten composable plugins.
deep-wiki
deep-wiki. Harness layer for Claude Code & Codex: plan-first development, independent review, durable long-running orchestration, and knowledge capture — ten composable plugins.