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/luanmorenommaciel/agentspec/readmegit clone --depth 1 https://github.com/luanmorenommaciel/agentspecWrote 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/luanmorenommaciel/agentspec/readme)<a href="https://agentmods.dev/agents/luanmorenommaciel/agentspec/readme"><img src="https://agentmods.dev/badge/agents/luanmorenommaciel/agentspec/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.04704 |
| Opus 5 | $0.00000 | $0.02352 |
| Sonnet 5 | $0.00000 | $0.00941 |
| Haiku 4.5 | $0.00000 | $0.00470 |
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 2d 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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentSpec Agents
AgentSpec deploys 58 specialized agents across 8 categories, each built on a three-tier template system with mandatory KB-First knowledge resolution. Every agent carries a cognitive framework that enforces structured confidence scoring, provenance tracking, and explicit stop conditions -- turning raw LLM capability into disciplined, auditable domain expertise.
58 agents | 8 categories | 3 tiers (T1/T2/T3) | 24 KB domains | 100% template compliance
How Agents Work (Cognitive Architecture)
AgentSpec agents are not raw LLM prompts. They operate through a three-layer cognitive architecture that separates routing, reasoning, and domain knowledge.
Layer 1: Claude Code Orchestrator (Router)
The orchestrator is Claude Code itself. It reads all 58 agent description fields from frontmatter, pattern-matches user messages to agent capabilities, and launches the best-fit agent. The orchestrator:
- Maintains memory, tasks, and plans across messages
- Selects agents based on trigger phrases, file types, and context
- Receives structured responses with confidence scores
- Is a generalist -- it knows WHO to call, not HOW to do the work
Layer 2: Agent Template (Cognitive Framework)
Every agent inherits from _template.md, which defines structured thinking:
- KB-First Resolution -- check local knowledge before external sources
- Agreement Matrix -- structured confidence scoring (KB vs MCP alignment)
- Impact Tiers -- CRITICAL/IMPORTANT/STANDARD/ADVISORY with thresholds
- Stop Conditions -- agents know when to REFUSE or ESCALATE
- Provenance -- every response cites confidence score and sources
Layer 3: Agent Instance (Domain Specialist)
Each agent adds domain-specific knowledge, capabilities, quality gates, and anti-patterns on top of the template framework. This layer carries the expertise -- dbt, Spark, Fabric, Airflow, and so on.
Request Flow
User
|
v
Orchestrator (Claude Code)
|-- reads 58 agent descriptions from frontmatter
|-- pattern-matches message to capabilities
|-- selects best-fit agent
v
Agent Instance
|-- KB-First: read .claude/kb/{domain}/
|-- Agreement Matrix: calculate confidence
|-- Impact Tier: check threshold for task type
|-- Execute (confidence met) or Stop (below threshold)
v
Response with Provenance
|-- confidence score
|-- sources cited (KB file, MCP query, codebase path)
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.
- 2d ago First seen · 374 lines · 0 tokens per session scan A 2ec65b98aa56
README is an agent published in the GitHub repository luanmorenommaciel/agentspec (244 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,704 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-09-01.
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.