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-modify-requirement)<a href="https://agentmods.dev/commands/emasoft/ai-maestro-architect-agent/amaa-modify-requirement"><img src="https://agentmods.dev/badge/commands/emasoft/ai-maestro-architect-agent/amaa-modify-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-modify-requirement"><img src="https://agentmods.dev/badge/commands/emasoft/ai-maestro-architect-agent/amaa-modify-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.00583 |
| Opus 5 | $0.00007 | $0.00292 |
| Sonnet 5 | $0.00003 | $0.00117 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
amaa-modify-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 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modify Requirement Command
Change the specifications of an existing requirement section or module during Plan Phase.
Usage
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/amaa_modify_requirement.py" modify $ARGUMENTS
Arguments
| Argument | Required | Description |
|---|---|---|
TYPE |
Yes | Type to modify: requirement or module |
ID |
Yes | ID of the requirement section or module |
--name |
No | New display name |
--criteria |
No | New acceptance criteria (modules only) |
--status |
No | New status: pending, in_progress, complete |
--priority |
No | New priority: critical, high, medium, low |
Modifying a Requirement Section
/amaa-modify-requirement requirement "Functional Requirements" --status complete
Marks the Functional Requirements section as complete.
Modifying a Module
/amaa-modify-requirement module auth-core --criteria "Support JWT and session tokens" --priority critical
Updates the auth-core module with new acceptance criteria and priority.
What Can Be Modified
| Field | Requirements | Modules |
|---|---|---|
| name | ✓ | ✓ |
| status | ✓ | ✓ |
| criteria | ✗ | ✓ |
| priority | ✗ | ✓ |
Restrictions
- Cannot modify modules with status
in_progressorcomplete - Cannot change the locked goal (requires user approval)
- Status changes are validated (cannot skip states)
Dynamic Flexibility
Modifications are reflected immediately in:
- The plan state file
- Exit criteria calculations
- Planning status display
Examples
# Mark a requirement section as complete
/amaa-modify-requirement requirement "API Requirements" --status complete
# Add criteria to an existing module
/amaa-modify-requirement module oauth-google --criteria "Support Google Workspace SSO"
# Change module priority
/amaa-modify-requirement module remember-me --priority low
# Rename a module
/amaa-modify-requirement module auth-2fa --name "Two-Factor Authentication"
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 · 87 lines · 14 tokens per session scan A f7841c0dc64d
amaa-modify-requirement is a command published in the GitHub repository Emasoft/ai-maestro-architect-agent (2 stars, last pushed 11d ago), licensed MIT. It adds 14 tokens to every session and 583 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.