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 skills add ucsandman/dashclaw-skills --skill manage-approvalsgit clone --depth 1 https://github.com/ucsandman/dashclaw-skillsWrote 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/ucsandman/dashclaw-skills/manage-approvals)<a href="https://agentmods.dev/skills/ucsandman/dashclaw-skills/manage-approvals"><img src="https://agentmods.dev/badge/skills/ucsandman/dashclaw-skills/manage-approvals/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/ucsandman/dashclaw-skills/manage-approvals"><img src="https://agentmods.dev/badge/skills/ucsandman/dashclaw-skills/manage-approvals.svg" alt="Reviewed on agentmods" width="80" 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.00015 | $0.01172 |
| Opus 5 | $0.00008 | $0.00586 |
| Sonnet 5 | $0.00003 | $0.00234 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
manage-approvals scanned grade A 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST "$DASHCLAW_BASE_URL/api/approvals/act_abc123" \ This is a copy
91% identical to manage-approvals — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Approvals
DashClaw's HITL (Human-in-the-Loop) system lets operators approve or deny agent actions before they execute. Three channels: dashboard, CLI, and SDK polling.
When Approvals Trigger
Approvals are triggered when:
- A guard policy returns
require_approval - An action's risk score exceeds the org's approval threshold
- The action touches systems flagged for mandatory review
The action enters pending_approval status and the agent waits.
Approval Channels
1. Dashboard (Web UI)
Navigate to the DashClaw dashboard → Mission Control or Decisions view. Pending approvals show with:
- Action type and declared goal
- Agent ID
- Risk score (color-coded)
- Systems touched
- Replay link for full decision context
Click Approve or Deny with optional reasoning.
2. CLI (Terminal)
# Interactive inbox — live updates via SSE
dashclaw approvals
# Direct approve/deny
dashclaw approve act_abc123 --reason "Reviewed deployment plan"
dashclaw deny act_abc123 --reason "Missing staging verification"
The interactive inbox (dashclaw approvals) uses SSE for real-time push notifications. New approval requests appear immediately without polling.
Keyboard shortcuts:
A— Approve selectedD— Deny selectedR— RefreshO— Open replay in browserQ— Quit
3. SDK Polling (Agent-Side)
// Agent waits for approval after guard returns require_approval
try {
await claw.waitForApproval(decision.action_id, {
timeout: 300000 // 5 minutes
});
console.log('Approved — proceeding');
} catch (err) {
if (err instanceof ApprovalDeniedError) {
console.log('Denied:', err.message);
return;
}
throw err;
}
try:
claw.wait_for_approval(decision["action_id"], timeout=300000)
print("Approved — proceeding")
except ApprovalDeniedError as e:
print(f"Denied: {e}")
return
4. API Direct
# Approve
curl -X POST "$DASHCLAW_BASE_URL/api/approvals/act_abc123" \
-H "x-api-key: $DASHCLAW_API_KEY" \
-H "Content-Type: application/json" \
-d '{"decision": "approved", "reasoning": "Reviewed and safe"}'
# Deny
curl -X POST "$DASHCLAW_BASE_URL/api/approvals/act_abc123" \
-H "x-api-key: $DASHCLAW_API_KEY" \
-H "Content-Type: application/json" \
-d '{"decision": "denied", "reasoning": "Risk too high"}'
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.
- 11d ago First seen · 155 lines · 15 tokens per session scan A 4bd20b1a40b2
manage-approvals is a skill published in the GitHub repository ucsandman/dashclaw-skills (2 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 1,172 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 91% identical to manage-approvals, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…