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/wildware-uk/agent-dashboard/dashboard-tasksgit clone --depth 1 https://github.com/wildware-uk/agent-dashboardWrote 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/wildware-uk/agent-dashboard/dashboard-tasks)<a href="https://agentmods.dev/commands/wildware-uk/agent-dashboard/dashboard-tasks"><img src="https://agentmods.dev/badge/commands/wildware-uk/agent-dashboard/dashboard-tasks.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.00015 | $0.00252 |
| Opus 5 | $0.00008 | $0.00126 |
| Sonnet 5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
dashboard-tasks 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 today.
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
Check the board.
list_tasks({ mine: true })— anything already yours and unfinished comes first. If a claimed task has had no update from you recently, it looks stalled to the owner: post one.list_tasks({ state: 'todo', project: $ARGUMENTS or omitted })— what is available.- Show me the list before claiming anything, unless I already told you to pick work up.
When you claim: claim_task({ task_id }). If it comes back conflict, somebody
else got it — do not retry it, list todo again and claim a different one.
While working a task, pass its task_id on every post_update. When it is done,
complete_task({ task_id, result }), with post_update on only if the finish is
worth a card of its own.
If you found follow-up work that is not yours to do now, create_task it rather
than mentioning it in an update nobody can track.
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.
- today First seen · 25 lines · 15 tokens per session scan A 55a8edfe9713
dashboard-tasks is a command published in the GitHub repository wildware-uk/agent-dashboard (0 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 252 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-09-04.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.