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 skills add Emasoft/ai-maestro-architect-agent --skill amaa-label-taxonomygit 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/skills/emasoft/ai-maestro-architect-agent/amaa-label-taxonomy)<a href="https://agentmods.dev/skills/emasoft/ai-maestro-architect-agent/amaa-label-taxonomy"><img src="https://agentmods.dev/badge/skills/emasoft/ai-maestro-architect-agent/amaa-label-taxonomy/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/skills/emasoft/ai-maestro-architect-agent/amaa-label-taxonomy"><img src="https://agentmods.dev/badge/skills/emasoft/ai-maestro-architect-agent/amaa-label-taxonomy.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.00046 | $0.00836 |
| Opus 5 | $0.00023 | $0.00418 |
| Sonnet 5 | $0.00009 | $0.00167 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
amaa-label-taxonomy 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 11d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AMAA Label Taxonomy
Overview
Provides the label taxonomy for the Architect Agent (AMAA) role. AMAA recommends component:* labels, validates effort:* estimates, and may suggest type:* changes based on architecture analysis. Each role plugin has its own label-taxonomy skill.
Prerequisites
- GitHub CLI (
gh) installed and authenticated - Active issue number for architecture work
- Familiarity with AMAA role (see AGENT_OPERATIONS.md)
Checklist
Copy this checklist and track your progress:
- Analyze requirements to identify affected components
- Review
priority:*labels to scope design constraints - Validate
effort:*against design complexity - Recommend
component:*labels from module breakdown - Create sub-issues with
type:*,component:*,status:backlog - Update effort label if architecture reveals mismatch
- Ensure all labels set before handoff to AMOA
Instructions
- Analyze requirements to identify affected components
- Review
priority:*labels to scope design constraints - Validate
effort:*against design complexity - Recommend
component:*labels from module breakdown - Create sub-issues with
type:*,component:*,status:backlog - Update effort label if architecture reveals mismatch
- Ensure all labels set before handoff to AMOA
Reference Documents
| Document | Description |
|---|---|
| label-taxonomy-details.md | Component Labels (component:*), Kanban Columns (Canonical 5-Column System), Type Labels AMAA Clarifies, Priority Labels (priority:*) - Read by AMAA, Effort Labels (effort:*) - Validated by AMAA, Architecture-to-Labels Mapping, Architecture Breakdown |
| examples-extended.md | Extended examples with bash commands (Example 1: Adding Component Labels After Architecture Analysis, Example 2: Validating Effort Estimate, Example 3: Creating Component-Specific Sub-Issues, Example 4: Architecture Decision Record (ADR)) |
| op-add-component-labels.md | Purpose, When to Use, Prerequisites, Procedure, Example, Component Label Reference, Error Handling |
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 82 lines · 46 tokens per session scan A d65c9134c8e1
amaa-label-taxonomy is a skill published in the GitHub repository Emasoft/ai-maestro-architect-agent (2 stars, last pushed 13d ago), licensed MIT. It adds 46 tokens to every session and 836 once invoked, about $0.0002 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 skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.