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/Emasoft/ai-maestro-architect-agentWrote 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-cicd-designer)<a href="https://agentmods.dev/agents/emasoft/ai-maestro-architect-agent/amaa-cicd-designer"><img src="https://agentmods.dev/badge/agents/emasoft/ai-maestro-architect-agent/amaa-cicd-designer/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-cicd-designer"><img src="https://agentmods.dev/badge/agents/emasoft/ai-maestro-architect-agent/amaa-cicd-designer.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.00026 | $0.01958 |
| Opus 5 | $0.00013 | $0.00979 |
| Sonnet 5 | $0.00005 | $0.00392 |
| Haiku 4.5 | $0.00003 | $0.00196 |
Grade A, and why
amaa-cicd-designer 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 10d 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 — 142 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 designing a pipeline, read the board and search for an existing card:
ama-kanban-render and ama-trdd-find.
- 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). CI/release-surface and baseline-deviation work ismanager— file it and move on. - 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.
- 10d ago First seen · 142 lines · 26 tokens per session scan A e2f9088f6c20
amaa-cicd-designer is an agent published in the GitHub repository Emasoft/ai-maestro-architect-agent (2 stars, last pushed 12d ago), licensed MIT. It adds 26 tokens to every session and 1,958 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
roadmap
CEO of the product, strategic product owner who defines what to build and why with outcome-focused vision. Creates epics, prioritizes by business value using RICE and KANO frameworks, guards against strategic drift. Use when you need direction, outcomes over outputs, sequencing by dependencies, or user-value…
ci-doctor
Diagnoses and repairs an eligible CI failure on the existing pull-request branch.
meeting-organizer
Prepare and summarize meeting docs.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
platform-engineer
Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.