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/reject-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/reject-task)<a href="https://agentmods.dev/commands/regardv/legendaryteam_for_claude/reject-task"><img src="https://agentmods.dev/badge/commands/regardv/legendaryteam_for_claude/reject-task.svg" alt="Measured on agentmods" 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.00407 |
| Opus 5 | $0.00000 | $0.00204 |
| Sonnet 5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
reject-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 8d 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
Reject Queued Task
Reject a task from the human review queue and prevent its execution.
Usage
When you see a task ID from /review-queue, use this command to reject it:
/reject-task [task-id] [optional reason]
What this command does
- Runs the rejection command via the review queue manager
- Removes task from the review queue
- Notifies @chief that task is rejected
- Logs the rejection decision for future confidence learning
- Updates statistics (rejection rate, reasons)
Implementation
Execute the following:
node scripts/review-queue-manager.js reject {{TASK_ID}} "{{REASON}}"
Where:
{{TASK_ID}}is the review queue task ID (e.g., "review-002"){{REASON}}is optional rejection reason
After rejection:
- Display confirmation message
- Ask if alternative approach desired
- Update @chief's confidence model
- Log for future learning
Example output:
❌ Task Rejected: Microservices Architecture
Details:
• Task ID: review-002
• Confidence: 55%
• Wait time: 20 minutes
• Rejection reason: "Timeline too long, prefer modular monolith approach first"
Impact:
📉 Future similar tasks will have reduced confidence
📝 Decision logged for learning
🔄 Blocked dependent tasks: payment-service, notification-service
@chief has been notified and will adjust confidence model accordingly.
Would you like to:
1. Propose an alternative approach?
2. Request a revised plan with different parameters?
3. Defer this task to a later phase?
Then notify @chief:
"@chief: Task review-002 has been rejected by human with reason: [reason]. Please:
- Update confidence model for similar tasks
- Log rejection for future learning
- If dependent tasks exist, queue them for alternative approaches"
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.
- 8d ago First seen · 69 lines · 0 tokens per session scan A e797e0afbd17
reject-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 407 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
send
Send a message to a running agent session. Use this to correct or direct a live agent mid-stream without killing and respawning it.
plan-workflow
Generate a skill chain plan for a high-level goal by analyzing the skills registry for input/output compatibility.
statusline
Show the governor fleet in your Claude Code statusline. Explicit, opt-in, and chains — it never replaces an existing statusline.
mpm-init
Initialize or update project for Claude Code and MPM.
orquestar
Macro (4 fases) vs micro (8 pasos): el core del DT resume el flujo en 4 fases (Clarificar → Planificar y validar → Ejecutar → Entregar). Este comando es el desglose en 8 pasos; no es un pipeline alternativo. Fuente canónica del par macro/micro: regla 00-orquestador-core (no redefinir el modelo en otros lugares…
init-rules
Auto-generate .claude/rules/ — path-scoped coding conventions from project analysis. Re-run after codebase changes to update rules while preserving manually added conventions.