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 dashclaw-platform-intelligencegit 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/dashclaw-platform-intelligence)<a href="https://agentmods.dev/skills/ucsandman/dashclaw-skills/dashclaw-platform-intelligence"><img src="https://agentmods.dev/badge/skills/ucsandman/dashclaw-skills/dashclaw-platform-intelligence.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.00056 | $0.06850 |
| Opus 5 | $0.00028 | $0.03425 |
| Sonnet 5 | $0.00011 | $0.01370 |
| Haiku 4.5 | $0.00006 | $0.00685 |
Grade A, and why
dashclaw-platform-intelligence 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 761 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DashClaw Platform Intelligence
Shape snapshot: sha1:0ccfae8317832d16a9090c614263b2d7a6693775
This file is auto-generated. Do not edit by hand — regenerate with:
python -m livingcode emit skill --output <path-to-SKILL.md>
Prefer Live Queries
The facts below are a snapshot. Before answering any question about DashClaw's current structure, routes, env vars, or schema — run a live query:
python -m livingcode query summary # High-level shape
python -m livingcode query routes # Current API surface
python -m livingcode query env # Current env vars
python -m livingcode query tables # Current schema
python -m livingcode query all --json # Full machine-readable shape
If the snapshot below disagrees with a live query, trust the live query.
Fallback: no Python, livingcode, or repo checkout
python -m livingcode only works where the livingcode package and the repo
checkout are present (e.g. a developer machine). In OpenClaw / the Claude app
neither exists. When you cannot run the queries above, fall back in this order:
GET {baseUrl}/api/doctor— live route/shape health straight from the running instance. Requires the workspace API key (x-api-key: <key>); returns 401/403 without it. This is the authoritative live source when the CLI is unavailable.- Read the committed static shape if a repo checkout is reachable:
app/lib/doctor/generated/shape.json(full machine-readable shape) anddocs/api-inventory.json(route inventory). These are regenerated on everynpm run livingcode:refresh, so they track the same facts the queries return. - Otherwise, treat the snapshot in this SKILL.md as authoritative — it is the best available source when neither the API nor the repo can be reached.
At a Glance
- 253 active API routes across 62 categories
- 4 required + 139 optional environment variables
- 93 database tables
API Surface
actions
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 761 lines · 56 tokens per session scan A e2b036808192
dashclaw-platform-intelligence is a skill published in the GitHub repository ucsandman/dashclaw-skills (2 stars, last pushed 24d ago), licensed MIT. It adds 56 tokens to every session and 6,850 once invoked, about $0.0003 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.