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-remove-requirement)<a href="https://agentmods.dev/commands/emasoft/ai-maestro-architect-agent/amaa-remove-requirement"><img src="https://agentmods.dev/badge/commands/emasoft/ai-maestro-architect-agent/amaa-remove-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-remove-requirement"><img src="https://agentmods.dev/badge/commands/emasoft/ai-maestro-architect-agent/amaa-remove-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.00720 |
| Opus 5 | $0.00007 | $0.00360 |
| Sonnet 5 | $0.00003 | $0.00144 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
amaa-remove-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 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remove Requirement Command
Remove a requirement section or module from the current plan. Only items with pending or planned status can be removed.
Usage
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/amaa_modify_requirement.py" remove $ARGUMENTS
Arguments
| Argument | Required | Description |
|---|---|---|
TYPE |
Yes | Type to remove: requirement or module |
ID |
Yes | ID of the requirement section or module |
--force |
No | Skip confirmation prompt |
Removing a Requirement Section
/amaa-remove-requirement requirement "Legacy Support"
Removes the "Legacy Support" requirement section if it has pending status.
Removing a Module
/amaa-remove-requirement module legacy-api
Removes the legacy-api module if it has planned or pending status.
Restrictions
Cannot remove items that are:
- In progress (
in_progressstatus) - Complete (
completestatus) - Already have GitHub Issues assigned
Rationale: Once work has started, the orchestrator must complete it. Use /amaa-modify-requirement to adjust scope instead.
Dynamic Flexibility
When you remove an item:
- It is immediately removed from the plan state file
- Stop hook no longer blocks exit for that item
- Exit criteria are recalculated without the removed item
Before removal:
- Modules: [A: done, B: in_progress, C: pending]
- Pending: 2
/amaa-remove-requirement module C
After removal:
- Modules: [A: done, B: in_progress]
- Pending: 1
State File Update
The command updates .claude/orchestrator-plan-phase.local.md:
Before:
modules:
- id: "auth-core"
status: "planned"
- id: "legacy-api"
status: "planned"
After /amaa-remove-requirement module legacy-api:
modules:
- id: "auth-core"
status: "planned"
Examples
# Remove a pending requirement section
/amaa-remove-requirement requirement "Legacy Compatibility"
# Remove a planned module
/amaa-remove-requirement module oauth-facebook
# Remove with force (skip confirmation)
/amaa-remove-requirement module oauth-twitter --force
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 · 116 lines · 14 tokens per session scan A 1a838a87ba85
amaa-remove-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 720 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.