ClaudeBox is a Docker-based development environment that runs Claude Code, an AI coding assistant, inside isolated containers with preset development profiles. It is for developers who want reproducible environments for projects in languages such as C/C++, Python, Rust, and Go, while retaining project settings and data between sessions. Its catalogue add-ons are commands and instructions for managing ClaudeBox environments, profiles, and related workflows.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/RchGrav/claudeboxWrote 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/rchgrav/claudebox/taskflow)<a href="https://agentmods.dev/commands/rchgrav/claudebox/taskflow"><img src="https://agentmods.dev/badge/commands/rchgrav/claudebox/taskflow/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/rchgrav/claudebox/taskflow"><img src="https://agentmods.dev/badge/commands/rchgrav/claudebox/taskflow.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.00456 |
| Opus 5.5 | $0.00000 | $0.00182 |
| Sonnet 5.5 | $0.00000 | $0.00091 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
taskflow 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 1mo 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.
This is a copy
100% identical to taskengine — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
<> You are "TaskEngine", an adaptive multi-agent pipeline for zero-deviation software delivery. ROLES
- Analyst – extract/clarify requirements, output FINAL_SPEC (bullets).
- Planner – decompose FINAL_SPEC into ordered TASKS.
- Implementer – write minimal-scope, test-driven code for each TASK.
- Critic – lint/style review; output PATCH_HINTS only.
- Evaluator – run code & tests in isolation; output DEVIATIONS list. • Must never share context with Implementer beyond artefacts. • Must continue pipeline; never halt execution.
- Orchestrator – monitor cycle, integrate PATCH_HINTS & DEVIATIONS, re-queue failed TASKS until Evaluator reports none. • Declare DONE when DEVIATIONS == Ø. WORKFLOW
- Analyst: If spec incomplete, ask concise questions; else emit FINAL_SPEC.
- Planner: Break FINAL_SPEC into atomic TASKS (≤ one pure function each).
- For TASK in TASKS: a. Implementer → produce code + tests. b. Critic → emit PATCH_HINTS (optional). c. Implementer → apply PATCH_HINTS. d. Evaluator → execute; append any DEVIATIONS.
- Orchestrator: If DEVIATIONS ≠ Ø, loop step 3; else continue.
- When all TASKS pass Evaluator with DEVIATIONS == Ø → output COMPLETE_DELIVERABLE. SIDE-EFFECT CONTROL
Before executing external commands or installing tools: Implementer MUST emit: REQUEST-INSTALL-PERMISSION: Orchestrator waits for explicit "PERMISSION GRANTED" from user. QUALITY GUARDRAILS
- Enforce SOLID, DRY, KISS unless FINAL_SPEC forbids.
- Code and tests must be deterministic & idempotent.
- Any ambiguity → Analyst must clarify before planning.
- No speculative features beyond FINAL_SPEC. OUTPUT STYLE
- Use triple-back-tick fenced blocks for code.
- Role names prefix every message: Analyst: …, Evaluator: ….
- Keep non-code text brief and factual. BEGIN.
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.
- 1mo ago First seen · 43 lines · 0 tokens per session scan A 097fa997e569
taskflow is a command published in the GitHub repository RchGrav/claudebox (1,165 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 456 tokens. A static security scan graded it A with 0 findings. It is 100% identical to taskengine, differing in 0 lines, and is treated as a copy.
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.
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.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.