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/chroniclergit 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/chronicler)<a href="https://agentmods.dev/commands/queelius/claude-anvil/chronicler"><img src="https://agentmods.dev/badge/commands/queelius/claude-anvil/chronicler.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.00045 | $0.01591 |
| Opus 5 | $0.00023 | $0.00796 |
| Sonnet 5 | $0.00009 | $0.00318 |
| Haiku 4.5 | $0.00005 | $0.00159 |
Grade A, and why
chronicler 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/chronicler
Run when you remember (Friday afternoon, end of month, after a posting spree). The goal is to make "did I cross-post the recent stuff?" a one-prompt workflow.
Scope
Default: posts from the last 2w, all configured API platforms.
Override via argument: /chronicler 1m, /chronicler 3d, /chronicler 6w. Anything crier_search accepts as since.
Configured API platforms are usually devto, hashnode, bluesky, mastodon. Skip platforms in import mode (medium) or paste mode (twitter, threads, linkedin), they need browser/clipboard.
Workflow
1. Scan
Run crier_doctor() first and note any platform in an error state: skip those
platforms in the proposal (or flag them as "needs config fix") rather than
proposing actions guaranteed to fail at execute time.
Run crier_search(since=<scope>) to get recent files with metadata.
For each file, check status with crier_article(<canonical_url_or_file>). Note which platforms it's missing from.
Also run crier_missing(platforms=[devto, hashnode, bluesky, mastodon]) to catch tracked-but-incomplete posts.
Skip:
- Files with
draft: truein front matter - Files already on all 4 configured platforms
- Files where
crier_checkreports errors (broken, missing title, etc.)
2. Build proposals
For each candidate post, draft the cross-post plan:
- Long-form platforms (devto, hashnode): no rewrite needed, use the full body.
- Short-form platforms (bluesky, mastodon): generate a rewrite. Read the article first (use
Readtool on the source file), then write a rewrite that:- Leads with the most specific or provocative claim. Not "I wrote a post about X."
- Stays under the budget: crier appends
\n\n<canonical URL>before enforcing the platform limit, so budget = limit minus (URL length + 2). For typical metafunctor URLs that means bluesky ~230 chars (limit 300) and mastodon ~430 (limit 500). - Contains no canonical URL: crier appends it automatically.
- Doesn't say "new blog post" or "check out my latest." Just say the thing.
- Can be more nuanced on mastodon than bluesky. Bluesky is one punch.
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 · 126 lines · 45 tokens per session scan A 344110ba17e8
chronicler is a command published in the GitHub repository queelius/claude-anvil (2 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 1,591 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 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.
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.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.