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-askgit 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-ask)<a href="https://agentmods.dev/commands/wildware-uk/agent-dashboard/dashboard-ask"><img src="https://agentmods.dev/badge/commands/wildware-uk/agent-dashboard/dashboard-ask.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.00279 |
| Opus 5 | $0.00008 | $0.00139 |
| Sonnet 5 | $0.00003 | $0.00056 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
dashboard-ask 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
Ask the owner: $ARGUMENTS
Pick the kind by what you need back, and do not use text where a real control
would do:
- a value →
text - permission for one consequential thing →
confirm - one action out of several →
buttons - one item from a list →
choice - several →
multi_choice - something you drafted and are about to send →
form, with your draft indefault, your actions inoptions, and the field named bylabel
Phrase question so it is answerable without reading my transcript, and put the
context in detail. Pass project so the banner says what this is about.
Then wait properly: while the state comes back pending, keep calling
await_request with the request_id. Stop only on answered, timeout or
cancelled.
timeout and cancelled are not permission. If either comes back, do not do the
thing — post an update saying you are blocked, and tell me.
For a form, act on value.text, not on the draft you sent.
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 · 30 lines · 15 tokens per session scan A 336633f1d5ad
dashboard-ask 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 279 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.