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/queelius/claude-anvil/criernpx skills add queelius/claude-anvil --skill criergit clone --depth 1 https://github.com/queelius/claude-anvilWrote 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/queelius/claude-anvil/crier)<a href="https://agentmods.dev/skills/queelius/claude-anvil/crier"><img src="https://agentmods.dev/badge/skills/queelius/claude-anvil/crier.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.00039 | $0.00975 |
| Opus 5 | $0.00019 | $0.00487 |
| Sonnet 5 | $0.00008 | $0.00195 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
crier 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crier Cross-Posting
Crier cross-posts blog content to multiple platforms. The blog is the source of truth.
Division of labor:
- Crier MCP tools handle mechanics: publish, track, query, validate
- Claude handles judgment: rewrites, platform voice, user interaction
Platform Reference
| Platform | Mode | Limit | Short-form? | Notes |
|---|---|---|---|---|
| devto | API | none | No | Tags auto-sanitized |
| hashnode | API | none | No | |
| bluesky | API | 300 | Yes | Needs rewrite |
| mastodon | API | 500 | Yes | Needs rewrite |
| medium | import | none | No | User imports from canonical URL |
| paste | 280 | Yes | Copy-paste only | |
| threads | paste | 500 | Yes | Copy-paste only |
| paste | 3000 | No | Copy-paste only |
Rewrite Guidelines
When cross-posting to short-form platforms (bluesky, mastodon), write a rewrite
and pass it via crier_publish(rewrite_content=...).
Rules
- Lead with insight, not summary. Open with the most interesting idea.
- No meta-language. Don't say "New blog post" or "I wrote about."
- Crier appends the canonical URL automatically. Never include it in the rewrite.
- Match platform voice:
- Bluesky: conversational, personal, like talking to a friend
- Mastodon: slightly more formal, technical audience
- Budget for the appended URL. Crier appends
\n\n<canonical URL>to the rewrite and then enforces the platform limit on the combined text, so the real budget islimit - (URL length + 2): roughly 230 chars on Bluesky (limit 300) and 430 on Mastodon (limit 500) for typical metafunctor URLs. Over-budget rewrites fail at the confirmed publish step, not at preview.
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 · 86 lines · 39 tokens per session scan A 4241ffd918ad
crier is a skill published in the GitHub repository queelius/claude-anvil (2 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 975 once invoked, about $0.0002 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
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
alive:world
The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.
alive-people
Weekly -- cross-reference people mentions, nudge stale contacts.
alive-search
Search across all walnuts -- decisions, people, files, references, insights, log history.