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 create-policiesgit 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/create-policies)<a href="https://agentmods.dev/skills/ucsandman/dashclaw-skills/create-policies"><img src="https://agentmods.dev/badge/skills/ucsandman/dashclaw-skills/create-policies/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/create-policies"><img src="https://agentmods.dev/badge/skills/ucsandman/dashclaw-skills/create-policies.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.01339 |
| Opus 5 | $0.00008 | $0.00669 |
| Sonnet 5 | $0.00003 | $0.00268 |
| Haiku 4.5 | $0.00002 | $0.00134 |
Grade A, and why
create-policies 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 10d 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 -H "x-api-key: $DASHCLAW_API_KEY" $DASHCLAW_BASE_URL/api/policies This is a copy
100% identical to create-policies — 0 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Guard Policies
Help developers define, import, and test guard policies that control what agents can and cannot do.
Policy Types
| Type | Purpose | Example |
|---|---|---|
risk_threshold |
Block/warn when risk score exceeds limit | Block actions with risk > 80 |
action_type_restriction |
Allow/deny specific action types | Block security actions without approval |
approval_gate |
Require human approval for matching actions | Require approval for deploys |
webhook_check |
Call external endpoint for policy decision | Check Jira ticket status before deploy |
semantic_guardrail |
LLM-based content analysis | Block PII in action metadata |
Guard Modes
off— No policy enforcement (development only)warn— Log policy violations but allow executionenforce— Block policy violations (production recommended)
Defining Policies in YAML
Risk Threshold Policy
name: high-risk-blocker
type: risk_threshold
mode: enforce
conditions:
risk_score_min: 80
reversible: false
action: block
reason: "Irreversible actions with risk >= 80 require manual execution"
Action Type Restriction
name: no-unattended-deploys
type: action_type_restriction
mode: enforce
conditions:
action_types:
- deploy
- database
action: require_approval
reason: "Deploy and database actions require human approval"
Approval Gate
name: production-approval-gate
type: approval_gate
mode: enforce
conditions:
systems_touched:
- production
risk_score_min: 50
action: require_approval
reason: "Production access with risk >= 50 requires approval"
Cost Ceiling
name: cost-ceiling
type: risk_threshold
mode: enforce
conditions:
cost_estimate_max: 100.00
action: block
reason: "Actions exceeding $100 estimated cost are blocked"
Content Filter
name: no-secrets-in-metadata
type: semantic_guardrail
mode: enforce
conditions:
scan_fields:
- declared_goal
- output_summary
patterns:
- "password"
- "api_key"
- "secret"
action: block
reason: "Sensitive data detected in action metadata"
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.
- 10d ago First seen · 225 lines · 15 tokens per session scan A 7835331eb143
create-policies is a skill published in the GitHub repository ucsandman/dashclaw-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 1,339 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 100% identical to create-policies, differing in 0 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…