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.
npx agentmods add commands/rafaelkamimura/claude-tools/close-azure-taskgit clone --depth 1 https://github.com/rafaelkamimura/claude-toolsWrote 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/rafaelkamimura/claude-tools/close-azure-task)<a href="https://agentmods.dev/commands/rafaelkamimura/claude-tools/close-azure-task"><img src="https://agentmods.dev/badge/commands/rafaelkamimura/claude-tools/close-azure-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 | $0.00000 | $0.02518 |
| Opus 5 | $0.00000 | $0.01259 |
| Sonnet 5 | $0.00000 | $0.00504 |
| Haiku 4.5 | $0.00000 | $0.00252 |
Grade A, and why
close-azure-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 5d 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 — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Close Azure DevOps Work Item
Closes Azure DevOps work item after verifying completion, running final checks, and documenting resolution.
Purpose
- Safely close completed work items
- Verify all acceptance criteria met
- Document final resolution and verification
- Run quality checks before closure
- Maintain completion audit trail
Required MCP Setup
This command requires Azure DevOps MCP server to be installed and configured.
If not installed, follow: https://github.com/microsoft/azure-devops-mcp-server
Execution Steps
Step 1: Validate Input
Check if work item number was provided as argument.
If no work item number provided: Output: "Usage: /close-azure-task [work_item_number]
Example: /close-azure-task 12345" Exit command.
Step 2: Fetch Work Item Details
Use mcp__azuredevops__get_work_item tool (if available):
- work_item_id: [provided work item number]
If tool not available: Output: "Azure DevOps MCP server not configured.
Install and configure following: /fetch-azure-task documentation" Exit command.
If work item not found: Output: "Work item [number] not found or access denied." Exit command.
Extract work item information:
- Current state
- Work item type
- Title and description
- Acceptance criteria
- Related work items
- Assigned to
Step 3: Verify Work Item State
Check current state of work item.
If state is already "Closed": Output: "Work item #[ID] is already closed.
Closed Date: [closed date] Closed By: [closed by]
No action needed." Exit command.
If state is "New" or "Active": Output: "Warning: Work item #[ID] is currently '[state]', not 'Resolved'.
Typically work items should be:
- Developed (Active)
- Code reviewed (Resolved)
- Tested and verified
- Then closed
Do you want to proceed with closure anyway? (yes/no):" WAIT for user confirmation.
If user says no: Output: "Closure cancelled. Consider using /update-azure-task to set status to 'Resolved' first." Exit command.
Step 4: Run Pre-Closure Checks
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.
- 5d ago First seen · 409 lines · 0 tokens per session scan A dc663bc410fa
close-azure-task is a command published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,518 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-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.