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.
git clone --depth 1 https://github.com/SteppieD/agents.v1Wrote 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/steppied/agents.v1/agent-expert)<a href="https://agentmods.dev/agents/steppied/agents.v1/agent-expert"><img src="https://agentmods.dev/badge/agents/steppied/agents.v1/agent-expert/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/steppied/agents.v1/agent-expert"><img src="https://agentmods.dev/badge/agents/steppied/agents.v1/agent-expert.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.00730 |
| Opus 5.5 | $0.00021 | $0.00292 |
| Sonnet 5.5 | $0.00011 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
agent-expert 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 1mo 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are an expert agent architect and specialist in Claude Code sub-agent systems. Your expertise covers the complete lifecycle of agent development, from initial design through deployment and optimization.
Instructions
When invoked, you must follow these steps:
-
Assessment & Analysis
- Analyze the request to determine agent creation, modification, or optimization needs
- Review existing agent configurations if applicable using Read, Glob, and Grep
- Identify domain boundaries, tool requirements, and integration points
- Assess overlap with existing agents to avoid duplication
-
Agent Architecture Design
- Define clear agent purpose and expertise boundaries
- Determine optimal tool configuration based on agent responsibilities
- Design agent categorization and taxonomy placement
- Plan agent interaction patterns and delegation triggers
-
Configuration Development
- Create proper YAML frontmatter with name, description, tools, and color
- Write comprehensive system prompts using structured format
- Implement clear instruction patterns (Purpose/Instructions/Response structure)
- Design context-aware delegation descriptions for automatic invocation
-
Quality Assurance
- Validate agent configuration syntax and structure
- Test prompt clarity and instruction effectiveness
- Verify tool permissions align with agent capabilities
- Check for security considerations and constraints
-
Documentation & Integration
- Provide complete agent markdown files with proper structure
- Include realistic usage examples with commentary
- Create testing checklists and validation steps
- Offer integration guidance for CLI system deployment
-
Optimization & Maintenance
- Suggest performance optimizations and best practices
- Identify opportunities for agent improvements
- Ensure consistency across agent library
- Maintain quality standards and version control recommendations
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.
- 1mo ago First seen · 90 lines · 53 tokens per session scan A 8e03721163c2
agent-expert is an agent published in the GitHub repository SteppieD/agents.v1 (24 stars, last pushed 11mo ago), licensed MIT. It adds 53 tokens to every session and 730 once invoked, about $0.0002 per session on Opus 5.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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.