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/nmime/motiv-buy/readmegit clone --depth 1 https://github.com/nmime/motiv-buyWrote 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/nmime/motiv-buy/readme)<a href="https://agentmods.dev/agents/nmime/motiv-buy/readme"><img src="https://agentmods.dev/badge/agents/nmime/motiv-buy/readme.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.1 | $0.00000 | $0.00659 |
| Opus 5 | $0.00000 | $0.00329 |
| Sonnet 5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
README 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.
This is a copy
86% identical to Agents Directory — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 86 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.
- today First seen · 86 lines · 0 tokens per session scan A 8b94206f1d46
README is an agent published in the GitHub repository nmime/motiv-buy (0 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 659 tokens. A static security scan graded it A with 0 findings. It is 86% identical to Agents Directory, differing in 11 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.