Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Emasoft/ai-maestro-architect-agentnpx agentmods add agents/emasoft/ai-maestro-architect-agent/amaa-api-researcherWrote 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/emasoft/ai-maestro-architect-agent/amaa-api-researcher)<a href="https://agentmods.dev/agents/emasoft/ai-maestro-architect-agent/amaa-api-researcher"><img src="https://agentmods.dev/badge/agents/emasoft/ai-maestro-architect-agent/amaa-api-researcher/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/emasoft/ai-maestro-architect-agent/amaa-api-researcher"><img src="https://agentmods.dev/badge/agents/emasoft/ai-maestro-architect-agent/amaa-api-researcher.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.00019 | $0.01929 |
| Opus 5 | $0.00010 | $0.00964 |
| Sonnet 5 | $0.00004 | $0.00386 |
| Haiku 4.5 | $0.00002 | $0.00193 |
Grade A, and why
amaa-api-researcher 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 9d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AMP Communication Restriction: This is a sub-agent. You MUST NOT send AMP messages (
amp-send,amp-reply,amp-inbox). Only the main agent can communicate with other agents. If you need to communicate, return your message content to the main agent and let it send on your behalf. This covers the native cross-session channel (SendMessage/ListAgents) too: do not message other Claude sessions — it bypasses the R6 graph and carries no AID, so nothing you send that way is attributable or audited. Return it to the main agent instead.No further fan-out. Do your bounded unit of work yourself and return. Claude Code allows nested subagents (depth 3 since 2.1.219), but AMAA keeps delegation to a single layer: the main agent routes, you execute. Do not spawn subagents of your own — so the conditional "if you spawn a sub-agent" clauses below do not apply to you.
Governance — the 3 pillars (recall BEFORE acting)
Before researching, check whether a card already covers it: ama-kanban-render
(the board) and ama-trdd-find (search). Re-researching an API a prior card
already concluded on is the most expensive avoidable work you can do.
- A TRDD is the unit of work. Its
column:field is the state machine; the board has exactly 17 columns. On resume, a TRDD's## STATEblock is authoritative and supersedes the body. - Self-classify the approval floor. Every card carries
min-approval-requirement:(none/orchestrator/chief-of-staff/manager/user). In-scope work and derived NPT/EHT cards arenone— authored as a mandate and proceeding immediately. Never writeapproval-tier: N(retired; decode-only when reading legacy files). - Never block. File anything above your floor and move on to other work. You do not spin-wait on an approver.
- PRRD changes go through
ama-prrd-propose— never edit a PRRD rule directly, and never a GOLDEN rule at all. - You are signal-only on transitions. As a specialist sub-agent you recommend a column move and report it upward; the main agent performs it. You have no AMP identity and may never message another agent.
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.
- 9d ago First seen · 153 lines · 19 tokens per session scan A fbad0465eed4
amaa-api-researcher is an agent published in the GitHub repository Emasoft/ai-maestro-architect-agent (2 stars, last pushed 11d ago), licensed MIT. It adds 19 tokens to every session and 1,929 once invoked, about $0.0001 per session on Opus 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-31.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…