Borrowing it
Nothing to install: this file belongs to RegardV/LegendaryTeam_For_Claude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/RegardV/LegendaryTeam_For_Claude/main/.claude/commands/approve-task.mdgit clone --depth 1 https://github.com/RegardV/LegendaryTeam_For_ClaudeWrote 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/regardv/legendaryteam_for_claude/approve-task)<a href="https://agentmods.dev/commands/regardv/legendaryteam_for_claude/approve-task"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/approve-task/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/regardv/legendaryteam_for_claude/approve-task"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/approve-task.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.00000 | $0.00387 |
| Opus 5 | $0.00000 | $0.00193 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
approve-task 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.
What it actually says
Approve Queued Task
Approve a task from the human review queue and trigger its execution.
Usage
When you see a task ID from /review-queue, use this command to approve it:
/approve-task [task-id] [optional notes]
What this command does
- Runs the approval command via the review queue manager
- Removes task from the review queue
- Notifies @chief to spawn the appropriate team
- Logs the approval decision for future confidence learning
- Updates statistics (approval rate, wait time)
Implementation
Execute the following:
node scripts/review-queue-manager.js approve {{TASK_ID}} "{{NOTES}}"
Where:
{{TASK_ID}}is the review queue task ID (e.g., "review-001"){{NOTES}}are optional approval notes/modifications
After approval:
- Display confirmation message
- Show which team will handle the task
- Provide estimated completion time
- Notify that @chief will coordinate execution
Example output:
✅ Task Approved: OAuth 2.0 Integration
Details:
• Task ID: review-001
• Confidence: 45% → Upgraded to APPROVED
• Wait time: 15 minutes
• Approval notes: "Use Stripe Checkout, not raw API"
Next Steps:
🚀 Spawning Team 6: @SecurityAgent + @APIAgent
⏱️ Estimated completion: 25 minutes
📝 Decision logged for future confidence learning
@chief will now coordinate the execution and report back when complete.
Then notify @chief:
"@chief: Task review-001 has been approved by human. Please spawn the appropriate team and execute according to the plan at thoughts/shared/plans/[plan-file].md with the following approval notes: [notes]"
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 · 61 lines · 0 tokens per session scan A 3e8f52dfc673
approve-task is a command published in the GitHub repository RegardV/LegendaryTeam_For_Claude (19 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 387 tokens. 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-30.
Other commands, from other repositories
camp-init
Create a new camp with the standard directory structure. A camp was previously called a campaign; camp init is the same command either way.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
fest-list
List all festivals with their status and completion percentage.
fest-next
Get the next actionable festival task with full context.
factory-ticket
Implement exactly one already-claimed Linear ticket in the current worktree.
factory-report
Linear status report across configured repos — queue depth, triage backlog, ready-to-dispatch, blocked/held.