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-start-planning)<a href="https://agentmods.dev/commands/emasoft/ai-maestro-architect-agent/amaa-start-planning"><img src="https://agentmods.dev/badge/commands/emasoft/ai-maestro-architect-agent/amaa-start-planning/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-start-planning"><img src="https://agentmods.dev/badge/commands/emasoft/ai-maestro-architect-agent/amaa-start-planning.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.00012 | $0.00517 |
| Opus 5 | $0.00006 | $0.00259 |
| Sonnet 5 | $0.00002 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
amaa-start-planning 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start Planning Command
Enter Plan Phase Mode to create comprehensive requirements and design specifications BEFORE any implementation begins.
Usage
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/amaa_start_planning.py" $ARGUMENTS
What This Command Does
- Creates Plan Phase state file at
.claude/orchestrator-plan-phase.local.md - Locks the user goal (cannot be changed without user approval)
- Initializes requirements tracking with sections for:
- Functional Requirements
- Non-Functional Requirements
- Architecture Design
- Sets exit criteria that must be met before transition to Orchestration Phase
Plan Phase Activities
During Plan Phase, you will:
- Gather user goals and constraints
- Create USER_REQUIREMENTS.md
- Design system architecture
- Break down into modules/phases
- Define acceptance criteria per module
- Prepare GitHub Issues (created AFTER plan approval)
- Create Claude Tasks for orchestrator coordination duties
State File Created
The command creates .claude/orchestrator-plan-phase.local.md with YAML frontmatter tracking:
phase: "planning"status: "drafting|reviewing|approved"goalandgoal_lockedfieldsrequirements_sectionsprogressmodulesbreakdownexit_criteriachecklist
Exit Blocking
The stop hook will block exit while in Plan Phase until:
- USER_REQUIREMENTS.md is complete
- All modules defined with acceptance criteria
- User approves the plan
Next Steps After Starting
- Review
.claude/orchestrator-plan-phase.local.mdto see current progress - Use
/amaa-add-requirementto add requirements and modules - Use
/amaa-modify-requirementto refine specifications - Mark all requirements as complete when planning is done
Example
/amaa-start-planning "Build a user authentication system with OAuth2 support"
This will:
- Create the plan phase state file
- Lock the goal: "Build a user authentication system with OAuth2 support"
- Initialize empty requirements sections
- Enable the stop hook to enforce plan completion
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 · 74 lines · 12 tokens per session scan A 051eeb87a0ad
amaa-start-planning is a command published in the GitHub repository Emasoft/ai-maestro-architect-agent (2 stars, last pushed 11d ago), licensed MIT. It adds 12 tokens to every session and 517 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.