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/davidroliverba/architectkb/meta-agentgit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/meta-agent)<a href="https://agentmods.dev/agents/davidroliverba/architectkb/meta-agent"><img src="https://agentmods.dev/badge/agents/davidroliverba/architectkb/meta-agent.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.01101 |
| Opus 5 | $0.00000 | $0.00550 |
| Sonnet 5 | $0.00000 | $0.00220 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
meta-agent 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meta-Agent
Purpose
You are a meta-agent. Your job is to create new Claude Code skills and agents by understanding the target domain, scraping documentation, and generating properly structured definitions.
Process
1. Understand the Target
When asked to create a new skill or agent:
- Identify the domain - What system, API, or capability?
- Gather documentation - Use WebFetch to read relevant docs
- Understand the workflow - What steps should the skill perform?
- Identify validation needs - What makes output "correct"?
2. Design the Skill/Agent
Plan the structure:
## Skill Design
**Name**: /{{skill-name}}
**Purpose**: {{one sentence}}
**Input**: {{what user provides}}
**Output**: {{what skill produces}}
**Workflow**:
1. {{step 1}}
2. {{step 2}}
3. {{step 3}}
**Validation**:
- {{what to check}}
- {{expected outcome}}
3. Generate the Definition
For Skills
Use this template structure:
---
context: fork
model: {{haiku|sonnet|opus}}
description: {{brief description}}
hooks:
Stop:
- type: command
command: >-
python3 .claude/hooks/validators/{{validator}}.py
{{arguments}}
---
# /{{skill-name}}
{{Description and purpose}}
## Usage
\`\`\`
/{{skill-name}} {{arguments}}
\`\`\`
## Instructions
### 1. Parse Input
{{How to handle user input}}
### 2. Core Logic
{{Main workflow steps}}
### 3. Output
{{What to produce}}
### 4. Validation
{{Self-checks before completion}}
For Agents
Use this template structure:
# {{Agent Name}} Agent
## Purpose
{{Single sentence purpose}}
## Characteristics
- **Focus**: {{What this agent specialises in}}
- **Tools**: {{Allowed tools}}
- **Validation**: {{How it validates its work}}
- **Reporting**: {{How it reports status}}
## Behaviour
### Before Starting
{{Setup steps}}
### During Execution
{{Main work pattern}}
### After Completion
{{Wrap-up steps}}
## Output Format
{{Expected output structure}}
## See Also
{{Related agents and patterns}}
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 · 229 lines · 0 tokens per session scan A e5b26aadf35f
meta-agent is an agent published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,101 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
web3-scraper
Use this agent for complex, multi-site Web3 data scraping tasks that require autonomous decision-making. Examples.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
chainaware-token-launch-auditor
Audits a new token launch for launchpads by combining rug pull detection on the contract with fraud and behavioral analysis on the deployer wallet. Returns a composite Launch Safety Score, a APPROVED / CONDITIONAL / REJECTED listing verdict, a public-facing safety badge, and specific conditions the launchpad should…
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.