Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add Emasoft/ai-maestro-architect-agent/plugin install 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/commands/emasoft/ai-maestro-architect-agent/amaa-add-requirement)<a href="https://agentmods.dev/commands/emasoft/ai-maestro-architect-agent/amaa-add-requirement"><img src="https://agentmods.dev/badge/commands/emasoft/ai-maestro-architect-agent/amaa-add-requirement/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/commands/emasoft/ai-maestro-architect-agent/amaa-add-requirement"><img src="https://agentmods.dev/badge/commands/emasoft/ai-maestro-architect-agent/amaa-add-requirement.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.00014 | $0.00591 |
| Opus 5 | $0.00007 | $0.00296 |
| Sonnet 5 | $0.00003 | $0.00118 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
amaa-add-requirement 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Requirement Command
Add a new requirement section or module to the current plan during Plan Phase.
Usage
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/amaa_modify_requirement.py" add $ARGUMENTS
Arguments
| Argument | Required | Description |
|---|---|---|
TYPE |
Yes | Type to add: requirement or module |
NAME |
Yes | Name of the requirement section or module |
--criteria |
No | Acceptance criteria (for modules) |
--priority |
No | Priority level: critical, high, medium, low |
Adding a Requirement Section
/amaa-add-requirement requirement "Security Requirements"
This adds a new requirement section to track in USER_REQUIREMENTS.md.
Adding a Module
/amaa-add-requirement module "password-reset" --criteria "Users can reset password via email link" --priority high
This adds a new module to the plan with:
- Module ID:
password-reset - Name derived from ID
- Acceptance criteria specified
- Priority: high
Dynamic Flexibility
You can add requirements or modules at ANY time during Plan Phase:
- New requirements are immediately tracked
- New modules become part of the completion criteria
- Stop hook will block exit until ALL current items complete
State File Update
The command updates .claude/orchestrator-plan-phase.local.md:
For requirements:
requirements_sections:
- name: "Security Requirements"
status: "pending"
For modules:
modules:
- id: "password-reset"
name: "Password Reset"
status: "planned"
acceptance_criteria: "Users can reset password via email link"
priority: "high"
github_issue: null
Examples
# Add functional requirement section
/amaa-add-requirement requirement "API Requirements"
# Add a critical module
/amaa-add-requirement module "auth-2fa" --criteria "Support TOTP-based 2FA" --priority critical
# Add a low-priority enhancement module
/amaa-add-requirement module "remember-me" --criteria "Remember login for 30 days" --priority low
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 · 93 lines · 14 tokens per session scan A fdf2be154fe7
amaa-add-requirement is a command published in the GitHub repository Emasoft/ai-maestro-architect-agent (2 stars, last pushed 13d ago), licensed MIT. It adds 14 tokens to every session and 591 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.