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/ruvnet/sublinear-time-solver/readmegit clone --depth 1 https://github.com/ruvnet/sublinear-time-solverWhat 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.00017 | $0.00690 |
| Opus 5 | $0.00009 | $0.00345 |
| Sonnet 5 | $0.00003 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
Agents Directory 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- Agents Directory — 100% identical, 0 lines differ
- README — 86% identical, 169 lines differ
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Agents Directory Structure
This directory contains sub-agent definitions organized by type and purpose. Each agent has specific capabilities, tool restrictions, and naming conventions that trigger automatic delegation.
Directory Structure
.claude/agents/
├── README.md # This file
├── _templates/ # Agent templates
│ ├── base-agent.yaml
│ └── agent-types.md
├── development/ # Development agents
│ ├── backend/
│ ├── frontend/
│ ├── fullstack/
│ └── api/
├── testing/ # Testing agents
│ ├── unit/
│ ├── integration/
│ ├── e2e/
│ └── performance/
├── architecture/ # Architecture agents
│ ├── system-design/
│ ├── database/
│ ├── cloud/
│ └── security/
├── devops/ # DevOps agents
│ ├── ci-cd/
│ ├── infrastructure/
│ ├── monitoring/
│ └── deployment/
├── documentation/ # Documentation agents
│ ├── api-docs/
│ ├── user-guides/
│ ├── technical/
│ └── readme/
├── analysis/ # Analysis agents
│ ├── code-review/
│ ├── performance/
│ ├── security/
│ └── refactoring/
├── data/ # Data agents
│ ├── etl/
│ ├── analytics/
│ ├── ml/
│ └── visualization/
└── specialized/ # Specialized agents
├── mobile/
├── embedded/
├── blockchain/
└── ai-ml/
Naming Conventions
Agent files follow this naming pattern:
[type]-[specialization]-[capability].agent.yaml
Examples:
dev-backend-api.agent.yamltest-unit-jest.agent.yamlarch-cloud-aws.agent.yamldocs-api-openapi.agent.yaml
Automatic Delegation Triggers
Claude Code automatically delegates to agents based on:
- Keywords in user request: "test", "deploy", "document", "review"
- File patterns:
*.test.js→ testing agent,*.tf→ infrastructure agent - Task complexity: Multi-step tasks spawn coordinator agents
- Domain detection: Database queries → data agent, API endpoints → backend agent
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 · 89 lines · 17 tokens per session scan A 73d42cceae3a
Agents Directory is an agent published in the GitHub repository ruvnet/sublinear-time-solver (89 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 690 once invoked, about $0.0001 per session on Opus 5. 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 agents, from other repositories
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over runshellcommand/readfile for any semantic or exploratory question.
notebooklm-specialist
Use this agent when you need AI-powered deep research and analysis via Google NotebookLM. Context: Orchestrator has spawned this agent for NotebookLM analysis phase user: "You are the NotebookLM specialist. Research brief: [topic]. Notebook ID: abc123. Output: ./docs/research/..." assistant: "Reading my skills and…
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Grep/Glob/Read for any semantic or exploratory question.
semble-search
Code search agent for exploring any codebase. Use for finding code by intent, locating implementations, understanding how something works, or discovering related code. Prefer over Bash/Read for any semantic or exploratory question.