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 skills/ucsandman/dashclaw/dashclaw-weeklynpx skills add ucsandman/DashClaw --skill dashclaw-weeklygit clone --depth 1 https://github.com/ucsandman/DashClawWrote 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/dashclaw-weekly)<a href="https://agentmods.dev/skills/ucsandman/dashclaw/dashclaw-weekly"><img src="https://agentmods.dev/badge/skills/ucsandman/dashclaw/dashclaw-weekly.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.00064 | $0.00763 |
| Opus 5 | $0.00032 | $0.00381 |
| Sonnet 5 | $0.00013 | $0.00153 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
dashclaw-weekly 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 5d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DashClaw weekly digest
Turn the maintainer's log into a public weekly update Wes can paste to
Reddit unmodified. The story is the experiment: an AI maintains this repo
under a human-held constitution (MAINTAINER.md), and these are its
receipts.
Gather (in order)
- Cursor: find the last
<!-- digest-posted: YYYY-MM-DD -->marker indocs/maintainer-log.md. Cover everything after it. No marker → last 7 days. An explicit range in the user's args overrides both. - Log entries: read the covered entries in
docs/maintainer-log.md— they are the primary source (decisions, incidents, numbers). - Commits:
git log --oneline --no-merges --since=<cursor>on main — cross-check nothing shipped unlogged. If something did, say so in the digest (the gap is itself content) and append a catch-up log entry. - Dogfood stats (best-effort, skip silently if unavailable): with a
local instance running and
DASHCLAW_API_KEYin.env.local, GET/api/policies/summary(30-day decision outcome counts — label the window honestly) and/api/policies/proposals(open tuning proposals). These are the "the product governs its own maintainer" numbers.
Compose
One fenced code block, ready to paste. No hard wraps — one line per paragraph, blank lines between (Wes's standing formatting rule for copyable text). Plain language; define DashClaw terms on first use; no internal codenames, file paths only when they're the point.
Sections, in order, dropping any that are empty this week:
- Title:
DashClaw maintainer update — week of <date>(+ version if one shipped) - TL;DR: 2-3 sentences.
- Shipped: what landed, with version + one-line why-it-matters each.
- Decisions: the why behind non-obvious calls, from the log.
- Incident of the week: the most instructive failure, told straight — these are the credibility of the whole series. Never omit one that's in the log.
- The AI is governed by the product: dogfood stats when available.
- Next up: the next roadmap item, one line.
- Links: repo,
MAINTAINER.md,docs/plans/owner-roadmap.md,docs/maintainer-log.md.
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.
- 5d ago First seen · 60 lines · 64 tokens per session scan A 96bd995d744c
dashclaw-weekly is a skill published in the GitHub repository ucsandman/DashClaw (297 stars, last pushed today), licensed MIT. It adds 64 tokens to every session and 763 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-30.
Other skills, from other repositories
optimizer
Analyzes and automatically optimizes existing agents by improving system prompts and tool configuration.
text2agent
Creates new agents from user requirements by generating Python implementation and mcpconfig.
tiktok_download
Single-file TikTok/Douyin video download and traffic metrics via TikHub API using only httpx; optional persisted raw API JSON plus a stdlib post-processor emitting CSV and simplified JSON. Supports one URL or concurrent batch (max 10 workers). No dependency on any project codebase.
app_evaluator
A professional skill for App Evaluation (evaluating app's performance with score) and App Improvement (giving professional suggestions for improving the app's performance).
last_7_days_news
Search and summarize the latest 7 days of AI news and X discussions using public sources plus browser-based X collection. Use for recent AI news, trends, X discussions, industry briefs, and summaries organized into hot topics, viewpoints, and opportunity areas.
self_evolve
Use for framework-gated self-evolve workflows in AWorld: evolve skills, create trajectory-backed proposals, inspect self-evolve run artifacts, run aworld-cli optimize, or prepare verified apply decisions through aworld.selfevolve gates.