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/thapaliyabikendra/ai-artifactsWrote 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/thapaliyabikendra/ai-artifacts/agent-categories)<a href="https://agentmods.dev/agents/thapaliyabikendra/ai-artifacts/agent-categories"><img src="https://agentmods.dev/badge/agents/thapaliyabikendra/ai-artifacts/agent-categories.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.01069 |
| Opus 5 | $0.00000 | $0.00535 |
| Sonnet 5 | $0.00000 | $0.00214 |
| Haiku 4.5 | $0.00000 | $0.00107 |
Grade A, and why
agent-categories 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 8d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Categories
Agents are organized by role (what they ARE) into the following categories.
Category Overview
| Category | Purpose | Examples |
|---|---|---|
architects/ |
Design systems, plan implementations | backend-architect, business-analyst |
reviewers/ |
Analyze and critique | abp-code-reviewer, react-code-reviewer, security-engineer, qa-engineer |
engineers/ |
Build and implement | abp-developer, react-developer, devops-engineer |
specialists/ |
Deep domain expertise | debugger |
Decision Tree: Where Does My Agent Go?
Is it primarily about designing/planning? → architects/
Is it primarily about reviewing/critiquing? → reviewers/
Is it primarily about building/implementing? → engineers/
Does it have deep domain expertise? → specialists/
Category Details
Architects (architects/)
Purpose: Design systems, create specifications, make architecture decisions.
Characteristics:
- Focus on design over implementation
- Create documentation (TSD, ADRs, schemas)
- Make technology and pattern decisions
- Plan before building
Typical Tools: Read, Write, Glob, Grep
Examples:
backend-architect- API design, database schemasproduct-architect- BRDs, user stories, acceptance criteriafrontend-architect- Component architecture, state management
Reviewers (reviewers/)
Purpose: Analyze, audit, and critique code or systems.
Characteristics:
- Read-only operations (typically)
- Produce findings and recommendations
- Don't implement fixes directly
- Focus on quality and compliance
Typical Tools: Read, Glob, Grep
Examples:
abp-code-reviewer- Backend code quality, ABP patternsreact-code-reviewer- Frontend code quality, React patternssecurity-engineer- Security audits, STRIDE, OWASPqa-engineer- Test coverage, quality validation
Engineers (engineers/)
Purpose: Build and implement features, write code.
Characteristics:
- Write and edit code
- Follow specifications from architects
- Run builds and tests
- May auto-approve edits
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.
- 8d ago First seen · 167 lines · 0 tokens per session scan A 0bb46e7d2a73
agent-categories is an agent published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 5mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,069 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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
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.