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/DauQuangThanh/hanoi-rainbowWrote 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/dauquangthanh/hanoi-rainbow/tasks-to-ado)<a href="https://agentmods.dev/commands/dauquangthanh/hanoi-rainbow/tasks-to-ado"><img src="https://agentmods.dev/badge/commands/dauquangthanh/hanoi-rainbow/tasks-to-ado/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/dauquangthanh/hanoi-rainbow/tasks-to-ado"><img src="https://agentmods.dev/badge/commands/dauquangthanh/hanoi-rainbow/tasks-to-ado.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.00023 | $0.00455 |
| Opus 5 | $0.00012 | $0.00228 |
| Sonnet 5 | $0.00005 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
tasks-to-ado 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- rainbow.tasks-to-ado — 95% identical, 6 lines differ
What it actually says
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Outline
IMPORTANT: After creating all Azure DevOps work items, automatically generate a 'chore:' prefixed git commit message (e.g., 'chore: sync tasks to Azure DevOps work items') and commit any tracking files or metadata upon completion.
- Run
{SCRIPT}from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot"). - From the executed script, extract the path to tasks.
- Get the Git remote by running:
git config --get remote.origin.url
ONLY PROCEED TO NEXT STEPS IF THE REMOTE IS AN AZURE DEVOPS URL
Azure DevOps remotes can be in these formats:
https://dev.azure.com/{organization}/{project}/_git/{repository}https://{organization}.visualstudio.com/{project}/_git/{repository}https://{organization}.visualstudio.com/DefaultCollection/{project}/_git/{repository}[email protected]:v3/{organization}/{project}/{repository}
-
Extract the Azure DevOps organization and project from the remote URL based on the pattern detected.
-
For each task in the list, use the Azure DevOps MCP server to create a new work item in the project that matches the Git remote.
UNDER NO CIRCUMSTANCES EVER CREATE WORK ITEMS IN PROJECTS THAT DO NOT MATCH THE REMOTE URL
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.
- 11d ago First seen · 43 lines · 23 tokens per session scan A 4d25c368bf6f
tasks-to-ado is a command published in the GitHub repository DauQuangThanh/hanoi-rainbow (16 stars, last pushed 7mo ago), licensed MIT. It adds 23 tokens to every session and 455 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
team
The team command manages team members and messages for your Codev project. Team data is stored in codev/team/ and displayed in the Tower dashboard.
sddp-implement-qc-loop
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.
sddp-prd
Command description: Create or refine the canonical product document. Argument hint: [rough product idea, users, domain, or market opportunity] Command category: project-bootstrap Prerequisites: none.
sddp-amend
Command description: Propagate a bootstrap change across canonical project artifacts and the project plan. Argument hint: [project-level change to propagate across bootstrap artifacts] Command category: project-bootstrap Prerequisites: project-instructions, product-document, technical-context, project-plan.
sddp-analyze
Command description: Audit spec, plan, and tasks for consistency and quality. Argument hint: [optional: analysis focus or remediation request] Command category: feature-delivery Prerequisites: spec, plan, tasks.
sddp-clarify
Command description: Reduce ambiguity in the current feature specification. Argument hint: [optional: ambiguity focus or feature directory] Command category: feature-delivery Prerequisites: spec.