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 ric03uec/clawrium --skill daily-digestgit clone --depth 1 https://github.com/ric03uec/clawriumWrote 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/ric03uec/clawrium/daily-digest)<a href="https://agentmods.dev/skills/ric03uec/clawrium/daily-digest"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/daily-digest/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/ric03uec/clawrium/daily-digest"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/daily-digest.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00029 | $0.00808 |
| Opus 5.5 | $0.00012 | $0.00323 |
| Sonnet 5.5 | $0.00006 | $0.00162 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
daily-digest 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 2mo 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
daily-digest
Once per day, summarize what happened on ric03uec/clawrium in the
last 24 hours and post it to the project's home Discord channel.
Inputs (last 24h, in ric03uec/clawrium)
- Merged PRs — title, number, author, one-line summary you derive from the PR body.
- Issues opened — title, number, current labels.
- Issues closed — title, number, the closing PR if any.
- Your own run logs from the previous day (memory keyed
daily-digest:last-run). Use it to avoid repeating the same items.
Commands:
gh pr list --repo ric03uec/clawrium --state merged --search \
"merged:>$(date -u -d '24 hours ago' +%Y-%m-%dT%H:%M:%SZ)" \
--json number,title,author,body
gh issue list --repo ric03uec/clawrium --state open --search \
"created:>$(date -u -d '24 hours ago' +%Y-%m-%dT%H:%M:%SZ)" \
--json number,title,labels
gh issue list --repo ric03uec/clawrium --state closed --search \
"closed:>$(date -u -d '24 hours ago' +%Y-%m-%dT%H:%M:%SZ)" \
--json number,title,closedByPullRequestsReferences
Output
A single Discord message in the home channel, structured as:
**clawrium digest — <YYYY-MM-DD>**
**Shipped (N)**
- #<num> <title> — <one-line summary>
**Opened (N)**
- #<num> <title> — <labels>
**Closed (N)**
- #<num> <title> — closed by #<pr>
Quiet day: <only if nothing material happened>
Send via the hermes Discord channel adapter (the agent already has the home channel id bound). Do not open a thread; the message is the unit.
Voice
- Engineer to engineer. No marketing copy ("exciting", "robust", "delights"), no hedging through verbosity.
- Emoji only when it encodes information (✅ for a green CI run that unblocks a release; 🔒 for a security fix). Skip them for flair.
- Past tense for shipped; present tense for state ("Open: 14").
- If a single PR did the heavy lifting, say so explicitly — don't level the slope.
Hard constraints
- One message per day. Idempotent — re-runs within the same day update rather than duplicate (track the last-message id in skill memory).
- Never
@hereor@everyone. - If 0 PRs merged and 0 issues opened or closed, post a one-line "Quiet day on clawrium." entry — silence reads as "the bot is broken."
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.
- 2mo ago First seen · 90 lines · 29 tokens per session scan A b31b5ccabd34
daily-digest is a skill published in the GitHub repository ric03uec/clawrium (67 stars, last pushed 14d ago), licensed Apache-2.0. It adds 29 tokens to every session and 808 once invoked, about $0.0001 per session on Opus 5.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
python
Use when the task is Python itself, in any framework or none: PEP 695 generics, mypy --strict typing, dataclass/Protocol/TypedDict/Enum choices, asyncio.TaskGroup, stdlib idioms, src/ layout + pyproject.toml with uv, ruff+mypy+pytest gate. NOT a FastAPI/ASGI service (that is fastapi), NOT a deep pytest suite (that is…
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
telegram
Telegram Bot skill for sending and editing Telegram messages via Bot API. Use when Bub needs to: (1) Send a message to a Telegram user/group/channel, (2) Reply to a specific Telegram message with replytomessageid, (3) Edit an existing Telegram message, or (4) Push proactive Telegram notifications. Prefer rich…
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…
modern-python-toolchain
Modern Python project setup with uv, ruff, and pyright. Use when initializing a new Python project, configuring the Python environment, setting up linting/formatting, or when a project needs uv (the fast Python package manager). Trigger on: 'set up Python', 'new Python project', 'configure uv', 'install uv', 'ruff'…
vexor-cli
Semantic file discovery via vexor. Use whenever locating where something is implemented/loaded/defined in a medium or large repo, or when the file location is unclear. Prefer this over manual browsing.