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 cardstack/boxel --skill realm-historygit clone --depth 1 https://github.com/cardstack/boxelWrote 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/cardstack/boxel/realm-history)<a href="https://agentmods.dev/skills/cardstack/boxel/realm-history"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/realm-history/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/cardstack/boxel/realm-history"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/realm-history.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.00893 |
| Opus 5.5 | $0.00017 | $0.00357 |
| Sonnet 5.5 | $0.00009 | $0.00179 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
realm-history 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Realm history & indexing control
Two related concerns under one skill:
boxel realm history— manage local checkpoints stored in.boxel-history/inside the synced workspace directory. Checkpoints are created automatically byboxel realm syncand can be created manually. Restore rolls the local working tree back to a checkpoint.boxel realm wait-for-ready/boxel realm cancel-indexing— observe and steer the realm-server's indexing pipeline.
When the user asks to...
| Ask | Run |
|---|---|
| "show me the checkpoint history" | boxel realm history <local-dir> |
| "create a manual checkpoint" | boxel realm history <local-dir> -m "Before risky change" |
| "restore to checkpoint #3" | boxel realm history <local-dir> -r 3 |
| "wait until indexing finishes" / "is it done indexing?" | boxel realm wait-for-ready --realm <realm-url> |
| "cancel the current indexing job" / "stop the index" | boxel realm cancel-indexing --realm <realm-url> |
Typical sequencing
Before a destructive sync, snapshot the local state so you can roll back:
boxel realm history ./local-dir -m "Before bulk delete"
boxel realm sync ./local-dir https://app.boxel.ai/owner/realm/ --prefer-local --delete
boxel realm wait-for-ready --realm https://app.boxel.ai/owner/realm/
# verify; if bad:
boxel realm history ./local-dir -r 1
boxel realm sync ./local-dir https://app.boxel.ai/owner/realm/ --prefer-local
wait-for-ready is the right call before any read that should see the latest writes — including boxel search and boxel file read against newly-pushed content.
cancel-indexing is rarely needed. Use it when an indexing job is wedged on bad input and the user wants to clear the queue before pushing a fix.
Commands
Generated from the boxel-cli Commander tree by pnpm build:plugin. Edit prose outside the generated block — never inside it.
boxel realm history <local-dir>
View, restore, or create local checkpoints stored under .boxel-history/
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 · 85 lines · 43 tokens per session scan A c43d926eaed9
realm-history is a skill published in the GitHub repository cardstack/boxel (27 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 893 once invoked, about $0.0002 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-10-21.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.