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 commands/queelius/claude-anvil/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/commands/queelius/claude-anvil/crier)<a href="https://agentmods.dev/commands/queelius/claude-anvil/crier"><img src="https://agentmods.dev/badge/commands/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 | $0.00024 | $0.00419 |
| Opus 5 | $0.00012 | $0.00210 |
| Sonnet 5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
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 4d 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.
What it actually says
/crier
Run a cross-posting workflow for blog content.
Steps
-
Check status: Use
crier_search(since="1m")andcrier_missing(platforms=["devto","hashnode","bluesky","mastodon"])to find what needs publishing. If the user provided arguments (like a date range or platform), adjust accordingly. -
Summarize: Show the user what needs publishing, grouped by content item and platform. Highlight:
- How many items are unposted
- Which platforms are API (automatic) vs manual/import
- Which platforms need short-form rewrites
-
Get scope: Ask the user what they want to publish:
- Everything shown?
- A specific file?
- Only certain platforms?
- Only long-form? Only short-form?
-
Execute: For the chosen scope:
- API long-form (devto, hashnode):
crier_publish(file, platform)with confirmation - API short-form (bluesky, mastodon): Read article, write a rewrite, then
crier_publish(file, platform, rewrite_content=..., rewrite_author="claude-code") - Import (medium): Note the canonical URL for manual import
- Paste (twitter, threads, linkedin): Use CLI
crier publish --to <platform> --yes
- API long-form (devto, hashnode):
-
Report: Show results for all platforms.
Tips
- Use the
crierskill for rewrite guidelines and platform voice - For bulk operations with many items, dispatch the cross-poster agent
- For analysis (gap analysis, performance review), dispatch the auditor agent
- When writing rewrites, lead with the most interesting insight
- Crier appends the canonical URL automatically
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.
- 4d ago First seen · 40 lines · 24 tokens per session scan A cfa68bae3689
crier is a command published in the GitHub repository queelius/claude-anvil (2 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 419 once invoked, about $0.0001 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 commands, from other repositories
composite-actions
Generate, review, secure, and test composite GitHub Actions following best practices — full repo scaffold, interview-driven generation, PR creation on existing repos, SHA pinning, secrets-as-inputs, job summaries, and actionlint validation.
github-actions
Design, review, secure, and debug GitHub Actions workflows — reusable workflows, OIDC federation, SHA pinning, token scoping, promotion orchestration, and CI failure diagnosis.
datadog
Set up and troubleshoot Datadog — Agent deployment on Kubernetes, APM instrumentation, Log Management, Monitors, Dashboards, SLOs, Synthetic tests, and live incident investigation using the Datadog MCP server. Covers Terraform-managed Datadog resources.
fluxcd
FluxCD entry point — routes to the right workflow based on what you need. Live cluster issue → structured 5-workflow debug trace. Repo health check → 6-phase audit (discovery, validation, API compliance, best practices, security). Helm chart review → helmchart. Starts by asking one question to confirm the right mode.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.
terraform
Runs through the full Terraform validation pipeline — fmt, validate, tflint, security scan — and reviews a module or plan for blast radius, IAM risk, and state impact.