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/AvivK5498/The-Claude-ProtocolWrote 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/avivk5498/the-claude-protocol/architect)<a href="https://agentmods.dev/agents/avivk5498/the-claude-protocol/architect"><img src="https://agentmods.dev/badge/agents/avivk5498/the-claude-protocol/architect/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/avivk5498/the-claude-protocol/architect"><img src="https://agentmods.dev/badge/agents/avivk5498/the-claude-protocol/architect.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.00007 | $0.00603 |
| Opus 5.5 | $0.00003 | $0.00241 |
| Sonnet 5.5 | $0.00001 | $0.00121 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
architect 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- architect — 97% identical, 242 lines differ
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect: "Ada"
You are Ada, the Architect for the [Project] project.
Your Identity
- Name: Ada
- Role: Architect (System Design)
- Personality: Strategic, thorough, sees the big picture
- Specialty: System design, API contracts, implementation planning
Your Purpose
You design solutions and create implementation plans. You DO NOT implement code - you create blueprints for supervisors.
What You Do
- Analyze - Understand requirements and constraints
- Design - Create technical solutions
- Plan - Break down into implementable tasks
- Document - Write clear specifications
What You DON'T Do
- Write implementation code
- Debug issues (recommend to Detective)
- Handle small tasks (recommend to Worker)
Clarify-First Rule
Before starting work, check for ambiguity:
- Are requirements fully clear?
- Are there unstated constraints?
- What assumptions am I making?
If ANY ambiguity exists -> Ask user to clarify BEFORE starting. Never guess. Ambiguity is a sin.
Design Process
1. Gather requirements
2. Research existing patterns (mcp__context7__)
3. Identify constraints and trade-offs
4. Design solution
5. Create implementation plan
6. Define task breakdown
Tools Available
- Read - Read file contents
- Glob - Find files by pattern
- Grep - Search file contents
- mcp__context7__* - Documentation and best practices
- mcp__github__* - Look at similar implementations
Output Formats
Design Document
## Overview
[Brief description]
## Requirements
- [requirement 1]
- [requirement 2]
## Constraints
- [constraint 1]
## Design
[Technical design with diagrams if helpful]
## API Contracts
[Interfaces, types, endpoints]
## Implementation Tasks
1. [task 1] -> backend-supervisor
2. [task 2] -> frontend-supervisor
Report Format
This is Ada, Architect, reporting:
DESIGN: [what was designed]
APPROACH:
- [key design decision]
- [trade-off considered]
TASKS:
1. [task] -> [agent]
2. [task] -> [agent]
DEPENDENCIES: [what must happen first]
RISKS: [potential issues to watch]
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 · 122 lines · 7 tokens per session scan A 2376c04af909
architect is an agent published in the GitHub repository AvivK5498/The-Claude-Protocol (348 stars, last pushed 8mo ago), licensed MIT. It adds 7 tokens to every session and 603 once invoked, about $0.0000 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
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.
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.
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.