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/daffy0208/ai-dev-standards/readmegit clone --depth 1 https://github.com/daffy0208/ai-dev-standardsWrote 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/daffy0208/ai-dev-standards/readme)<a href="https://agentmods.dev/agents/daffy0208/ai-dev-standards/readme"><img src="https://agentmods.dev/badge/agents/daffy0208/ai-dev-standards/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 | $0.00000 | $0.00906 |
| Opus 5 | $0.00000 | $0.00453 |
| Sonnet 5 | $0.00000 | $0.00181 |
| Haiku 4.5 | $0.00000 | $0.00091 |
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 4d 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Agents
Claude Code provides specialized agent types that optimize for different development tasks. Each agent has unique capabilities and performance characteristics.
Available Agent Types
General-Purpose Agent (Default)
The standard Claude Code agent for most development tasks.
Use Cases:
- Code search and analysis
- Multi-step research tasks
- Complex codebase exploration
- File operations and editing
- General development assistance
Strengths:
- Searching for code, configurations, and patterns across large codebases
- Analyzing multiple files to understand system architecture
- Investigating complex questions requiring exploration of many files
- Performing multi-step research tasks
When to Use:
- Default choice for most development tasks
- When you need comprehensive analysis
- When task involves multiple files or complex relationships
Documentation: See general-purpose.md
Explore Agent
Fast codebase exploration with configurable thoroughness levels.
Use Cases:
- Initial repository assessment
- Architecture understanding
- Rapid codebase familiarization
- Pattern discovery
Modes:
- Quick: Fast overview, minimal depth
- Medium: Balanced exploration (default)
- Very Thorough: Deep analysis, maximum detail
When to Use:
- Starting work on unfamiliar codebase
- Need architectural overview
- Searching for patterns or conventions
- Building mental model of project
Documentation: See explore.md
Status Line Setup Agent
Configure status line display settings for Claude Code.
Use Cases:
- Customize CLI output format
- Configure status indicators
- Set up display preferences
When to Use:
- Initial setup
- Customizing CLI experience
- Adjusting output verbosity
Output Style Setup Agent
Create and manage output style configurations.
Use Cases:
- Customize output formatting
- Set up color schemes
- Configure display styles
When to Use:
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.
- 4d ago First seen · 178 lines · 0 tokens per session scan A 5cf140d59ebb
README is an agent published in the GitHub repository daffy0208/ai-dev-standards (36 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 906 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-30.
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.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.