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 skills/chan4lk/specclaw/azdo-issuenpx skills add chan4lk/specclaw --skill azdo-issuegit clone --depth 1 https://github.com/chan4lk/specclawWrote 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/skills/chan4lk/specclaw/azdo-issue)<a href="https://agentmods.dev/skills/chan4lk/specclaw/azdo-issue"><img src="https://agentmods.dev/badge/skills/chan4lk/specclaw/azdo-issue.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.00082 | $0.00624 |
| Opus 5 | $0.00041 | $0.00312 |
| Sonnet 5 | $0.00016 | $0.00125 |
| Haiku 4.5 | $0.00008 | $0.00062 |
Grade A, and why
azdo-issue 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 6d 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
specclaw azdo-issue
First, run specclaw-ensure-init .specclaw — idempotently creates .specclaw/ if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).
Create an Azure Boards Work Item from a specclaw change. Requires:
proposal.mdto exist (run/specclaw:proposefirst).azdo.boards.sync: trueand a validazdo.boards.work_item_typeinconfig.yaml.- ADO credentials already set up via
/specclaw:auth-azdo.
Subcommands
Create the Work Item:
specclaw-azdo-issue create .specclaw <change>
Idempotent — if a Work Item already exists for this change (recorded in status.md), exits with a warning and does not duplicate.
Update the Work Item description with the latest task checklist:
specclaw-azdo-issue update .specclaw <change>
Post a comment:
specclaw-azdo-issue comment .specclaw <change> "<comment text>"
Close (final comment + closed-by-specclaw tag, no state transition):
specclaw-azdo-issue close .specclaw <change>
Link a pull request to the Work Item:
specclaw-azdo-issue link-pr .specclaw <change> <project_id> <repo_id> <pr_id>
Called automatically by /specclaw:pr-azdo; rarely invoked directly.
Notes
- specclaw does not transition Work Item state. Auto-transitioning is too easy to break across ADO process templates (Agile / Scrum / Basic). Humans drive state in ADO; specclaw only writes description, comments, and tags.
- The Work Item is tagged with
azdo.boards.tag(defaultspecclaw) so you can filter specclaw items in Boards queries. - On archive, an additional
closed-by-specclawtag is added so completed changes are easy to find. - After creation, the Work Item ID and URL are saved to
.specclaw/changes/<change>/status.mdas**Azure Boards Work Item:** [#1234](url)— this line is also used for idempotency checks on subsequent runs.
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.
- 6d ago First seen · 49 lines · 82 tokens per session scan A d7274fc03fa9
azdo-issue is a skill published in the GitHub repository chan4lk/specclaw (12 stars, last pushed 2d ago), licensed MIT. It adds 82 tokens to every session and 624 once invoked, about $0.0004 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-30.
Other skills, from other repositories
moai-workflow-spec
SPEC workflow orchestration with EARS format requirements, acceptance criteria, and Plan-Run-Sync integration for MoAI-ADK development. Use when creating SPEC documents or defining acceptance criteria.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
moai-workflow-templates
Template management system for code boilerplates, feedback templates, scaffolding, and project optimization workflows. Use when creating templates, generating boilerplate files, or managing scaffolding.
moai-workflow-project
Integrated project management system covering documentation, language initialization, template optimization, docs generation, and JIT document loading. Absorbed from moai-workflow-templates, moai-docs-generation, and moai-workflow-jit-docs.
moai
MoAI unified orchestrator for autonomous development. Routes natural language or subcommands (plan, run, sync, project, fix, loop, mx, feedback, review, clean, codemaps, gate, e2e, harness, goal, todo) to specialized agents.