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/fetch-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/fetch-azure-task)<a href="https://agentmods.dev/commands/rafaelkamimura/claude-tools/fetch-azure-task"><img src="https://agentmods.dev/badge/commands/rafaelkamimura/claude-tools/fetch-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.01015 |
| Opus 5 | $0.00000 | $0.00508 |
| Sonnet 5 | $0.00000 | $0.00203 |
| Haiku 4.5 | $0.00000 | $0.00102 |
Grade B, and why
fetch-azure-task scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Command: `grep -q "^.claude/azure-tasks/" .gitignore || echo ".claude/azure-tasks/" >> .gitignore` How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fetch Azure DevOps Work Item
Retrieves and displays Azure DevOps work item details including description, acceptance criteria, related work, and current status.
Purpose
- Fetch work item data from Azure DevOps
- Display structured work item information
- Save work item context for reference during development
- Provide quick access to task requirements
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: /fetch-azure-task [work_item_number]
Example: /fetch-azure-task 12345" Exit command.
Step 2: Fetch Work Item Data
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: https://github.com/microsoft/azure-devops-mcp-server
Add to ~/.claude/mcp.json: { "mcpServers": { "azuredevops": { "command": "npx", "args": ["-y", "@azure/azure-devops-mcp-server"], "env": { "AZURE_DEVOPS_ORG_URL": "https://dev.azure.com/your-org\", "AZURE_DEVOPS_PAT": "your-personal-access-token" } } } }" Exit command.
If work item not found or access denied: Output: "Work item [number] not found or access denied.
Check:
- Work item number is correct
- You have permission to access this work item
- Azure DevOps PAT has sufficient permissions" Exit command.
Step 3: Parse Work Item Data
Extract from work item response:
- ID and title
- Work item type (User Story, Task, Bug, Feature)
- State (New, Active, Resolved, Closed)
- Assigned to
- Area path and iteration
- Description
- Acceptance criteria (if available)
- Related work items
- Tags
- Created date and updated date
- Priority and severity (if applicable)
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.
- 4d ago First seen · 169 lines · 0 tokens per session scan B b9ed4b953272
fetch-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 1,015 tokens. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
project-recap
Generate a visual project recap for context switching.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.
session-log
Create or append a session log entry.
my-tasks
Track, prioritize, and execute tasks with goal alignment and due date awareness. Claude doesn't just remind you — it helps get work done.