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 release-watchergit 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/release-watcher)<a href="https://agentmods.dev/skills/ric03uec/clawrium/release-watcher"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/release-watcher/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/release-watcher"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/release-watcher.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.00033 | $0.00961 |
| Opus 5.5 | $0.00013 | $0.00384 |
| Sonnet 5.5 | $0.00007 | $0.00192 |
| Haiku 4.5 | $0.00003 | $0.00096 |
Grade A, and why
release-watcher 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 1mo 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release-watcher
Once per day, scan upstream *Claw releases and the
ric03uec/clawrium GitHub Discussions for feature ideas that could
land in clawrium. Surface the top 3 candidates to Devashish via Discord
DM with an approve / skip pattern. On approval, file a GitHub issue.
Inputs
- Releases (last 7 days, GitHub API):
openclaw/openclawreleaseszeroclaw/zeroclawreleasesnousresearch/hermesreleases- Any additional supported
*Clawrepos listed inplatform/registry/*/manifest.yaml(look up dynamically; don't hardcode).
gh api repos/ric03uec/clawrium/discussions— open discussions updated in the last 7 days, sorted by reaction count.- Memory key
release-watcher:seen— release tag IDs already presented, so candidates don't repeat across days.
Scoring
Pick the 3 candidates that score highest on:
- User-facing: does this change something a clawrium user would directly touch (CLI, GUI, agent behavior, install flow)?
- Fits clawrium's surface: matches an existing primitive (agent type, integration, channel, skill) rather than introducing a new top-level concept.
- Cheap to land: rough fit in an afternoon's work, not a quarter.
Skip:
- Pure internal refactors in the upstream project.
- Features that depend on infrastructure clawrium does not have (custom kernels, GPU sharding, etc.).
- Anything already covered by an open issue (check before suggesting).
Output — Discord DM
Send a single DM to user 740723459344302120 (Devashish) in the
project guild. Slack is not used — the original issue proposed
Slack DM for this flow; release-watcher uses Discord DM in the same
guild instead.
Format:
Release watch — <YYYY-MM-DD> — 3 candidates
1. <project> <tag> — <one-line rationale>
<link>
2. <project> <tag> — <one-line rationale>
<link>
3. <project> <tag> — <one-line rationale>
<link>
Reply: `approve 1 2` to file issues, `skip all`, or `skip 3` to drop
the third while keeping 1+2 in tomorrow's pool.
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.
- 1mo ago First seen · 112 lines · 33 tokens per session scan A 404fd514a7e6
release-watcher is a skill published in the GitHub repository ric03uec/clawrium (67 stars, last pushed 10d ago), licensed Apache-2.0. It adds 33 tokens to every session and 961 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
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…
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…
pypi-release
This skill should be used when releasing tunacode-cli to PyPI. It keeps the existing local release checks, then hands the actual PyPI upload to a GitHub Actions workflow that uses the repository's PYPIAPITOKEN secret.
python-format
Formats Python files with ruff format and reports which files changed.
spawnpoint
This skill should be used when an agent needs to create, list, extend, or remove multi-repo git worktree workspaces using the spawnpoint CLI (binary spawnpoint, shell wrapper sp). Use it when a task involves spinning up isolated worktrees for a feature branch across one or more repos, finding existing workspaces…
agentic-preflight
Use when shipping a branch: reviewing, documenting, linting, testing, and pushing work through Agentic Preflight. Also use when a push is blocked by the agentic-preflight pre-push hook or when the user says agentic-preflight:uninstall to remove this tool from the current project.