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-taxonomy-opsgit 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-ops)<a href="https://agentmods.dev/skills/emasoft/ai-maestro-architect-agent/amaa-label-taxonomy-ops"><img src="https://agentmods.dev/badge/skills/emasoft/ai-maestro-architect-agent/amaa-label-taxonomy-ops/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-ops"><img src="https://agentmods.dev/badge/skills/emasoft/ai-maestro-architect-agent/amaa-label-taxonomy-ops.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.00039 | $0.00499 |
| Opus 5 | $0.00019 | $0.00249 |
| Sonnet 5 | $0.00008 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
amaa-label-taxonomy-ops 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 12d 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.
What it actually says
AMAA Label Taxonomy (Operations)
Overview
Operational procedures for the AMAA label taxonomy: validating effort estimates, creating component sub-issues from epics, and creating Architecture Decision Record (ADR) issues.
Prerequisites
- GitHub CLI (
gh) installed and authenticated
Instructions
- Validate effort labels against architecture complexity
- Create component-specific sub-issues from epics
- Create ADR issues for significant architectural decisions
- Link all sub-issues and ADRs to parent issues
Checklist
Copy this checklist and track your progress:
- Validate effort label matches architecture complexity
- Create sub-issues for each component identified
- Create ADR issues for significant decisions
- Link all created issues to parents
Reference Documents
| Document | Content |
|---|---|
| op-validate-effort-estimate.md | Purpose, When to Use, Prerequisites, Procedure, Example, Effort Guidelines, Error Handling |
| op-create-sub-issues.md | Purpose, When to Use, Prerequisites, Procedure, Example, Description, Error Handling |
| op-create-adr-issue.md | Purpose, When to Use, Prerequisites, Procedure, Example, Status, Error Handling |
Examples
Example: gh issue edit 123 --remove-label "effort:s" --add-label "effort:m" after architecture reveals higher complexity.
Error Handling
| Issue | Fix |
|---|---|
| No effort label found | Recommend effort based on analysis |
| Duplicate ADR number | Re-query and increment |
| Too many sub-issues | Combine related tasks |
Output
| Type | Description |
|---|---|
| Effort updates | CLI stdout confirmation |
| Sub-issue creation | New issue URLs |
| ADR issues | ADR issue URL with status |
Resources
See Reference Documents table above.
What ships with it
3 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.
- 12d ago First seen · 67 lines · 39 tokens per session scan A 3ebfe919cc61
amaa-label-taxonomy-ops is a skill published in the GitHub repository Emasoft/ai-maestro-architect-agent (2 stars, last pushed 13d ago), licensed MIT. It adds 39 tokens to every session and 499 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.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.