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 blog-authorgit 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/blog-author)<a href="https://agentmods.dev/skills/ric03uec/clawrium/blog-author"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/blog-author/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/blog-author"><img src="https://agentmods.dev/badge/skills/ric03uec/clawrium/blog-author.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.00897 |
| Opus 5.5 | $0.00012 | $0.00359 |
| Sonnet 5.5 | $0.00006 | $0.00179 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
blog-author 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
blog-author
Poll ric03uec/clawrium release tags every 30 minutes. For each new
tag, draft a short blog post per user-visible feature and open a PR
against blog/. The post is a draft for human review and editing —
never publish on your own.
Inputs
gh release list --repo ric03uec/clawrium --limit 5and the per-releasegh release view <tag> --json body,tagName,publishedAt.- The diff between the previous tag and this one for surface area
context:
git log <prev>..<tag>and selectivegit showon commits the release notes call out. - Existing scenarios under
scenarios/— the post must reference at least one runnable snippet (see "Output" below). - Memory key
blog-author:tagged— release tags already drafted.
Triage rule — what gets a post
Each user-visible feature in the release notes gets its own post. Bundled posts produce shallow writeups; split aggressively.
A change qualifies if it falls into one of:
- New
clawctlcommand, option, or workflow. - New agent type, integration, channel, or skill.
- New GUI route or page.
- Behavior change a user would notice on upgrade.
Skip:
- Internal refactors, dependency bumps, test changes.
- Documentation-only or scenario-only edits.
- Security fixes — let the maintainer write those by hand.
Output — PR
For each qualifying feature, open a PR against main titled:
blog: <tag> — <feature one-liner>
The PR adds one file: blog/<YYYY>-<MM>-<DD>-<slug>.md.
Required front-matter:
---
title: <feature one-liner>
date: <YYYY-MM-DD from release publishedAt>
tag: <release tag>
status: draft
author: maurice
---
Required structure (short — aim for ~250–400 words):
- What changed — one paragraph in engineer voice.
- Why — one paragraph, lifted/condensed from the release notes or linked issue. No marketing fluff.
- Try it — at least one runnable snippet from
scenarios/or built from the actual CLI signatures insrc/clawrium/cli/. The snippet must work on a fresh clawrium install at this tag. - Links — release notes URL, the primary PR(s).
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 · 107 lines · 29 tokens per session scan A d51df592dc32
blog-author is a skill published in the GitHub repository ric03uec/clawrium (67 stars, last pushed 10d ago), licensed Apache-2.0. It adds 29 tokens to every session and 897 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.