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.
npx agentmods add agents/joris887/exosuit/claudegit clone --depth 1 https://github.com/joris887/exosuitWrote 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/agents/joris887/exosuit/claude)<a href="https://agentmods.dev/agents/joris887/exosuit/claude"><img src="https://agentmods.dev/badge/agents/joris887/exosuit/claude.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.00288 |
| Opus 5 | $0.00000 | $0.00144 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
CLAUDE 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 3d 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
Agents Directory
Native Claude Code agents (subagents) that provide specialized personas for focused tasks.
Usage
- Invoked via
claude --agent <name>or from skills using subagent delegation - Each
.mdfile defines one agent persona with specific expertise and constraints - Agents inherit project rules and hooks — they are not independent of the framework
Available Agents
code-reviewer— PR and code review with checklist enforcementarchitecture-reviewer— architectural fitness evaluationcodebase-explorer— read-only exploration and analysisintegration-tester— independent dynamic verification (runs tests and commands)research-analyst— web research with source quality scoringsecurity-analyst— security-focused code auditspec-reviewer— specification and requirements reviewperformance-engineer— performance analysis and optimization
Important
Native agents are dispatch targets for skills and parallel review, NOT replacements for quality gate skills. For quality gates, use the skills (/code-quality, /security-audit, /architecture-check, /performance-check), not the agents directly.
Conventions
- Keep agent files under 100 lines — agents are personas, not encyclopedias
- Agents should reference project rules/docs by path, not inline content
- Never add tool permissions beyond what the agent's role requires
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.
- 3d ago First seen · 27 lines · 0 tokens per session scan A bc186ebad6b0
CLAUDE is an agent published in the GitHub repository joris887/exosuit (4 stars, last pushed 14d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 288 tokens. 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 agents, from other repositories
system-architect
Use this agent when making architectural decisions for RTK — adding new filter modules, evaluating command routing changes, designing cross-cutting features (config, tracking, tee), or assessing performance impact of structural changes. Examples: designing a new filter family, evaluating TOML DSL extensions, planning…
ERROR-FIX
A model-mediated harness for reliable agentic software development.
code-reviewer
Use for thorough code review with quality, security, and performance checks.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).