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 boxel-commandgit 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/boxel-command)<a href="https://agentmods.dev/skills/cardstack/boxel/boxel-command"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/boxel-command/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/boxel-command"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/boxel-command.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.00075 | $0.01535 |
| Opus 5.5 | $0.00030 | $0.00614 |
| Sonnet 5.5 | $0.00015 | $0.00307 |
| Haiku 4.5 | $0.00007 | $0.00153 |
Grade A, and why
boxel-command 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Boxel Host Commands
Some Boxel operations only exist inside the host app's prerendered runtime — there's no realm-server HTTP endpoint for them, and they can't be reimplemented in plain Node. The realm server's /_run-command endpoint forwards a job to the prerenderer (a headless Chrome instance that has the full host runtime loaded), executes the named command there, and returns the serialized result. Schema introspection, module evaluation, card instantiation, transpiled-module fetches — all of these go through run-command.
This skill documents how to invoke that flow.
When to use it
- Card type schema lookup. Get the live
{ attributes, relationships }JSON Schema for aCardDefby introspecting its real class at runtime — not by reading the.gtssource. - Module evaluation. Load a
.gts/.tsmodule in the prerender sandbox to surface broken imports, circular references, or top-level runtime errors before they hit a real consumer. - Card instantiation. Construct a card instance from a JSON document inside the prerender — exercises the
CardDefclass against the document shape. - Anything else exposed at
@cardstack/boxel-host/commands/<name>/default. Each module is its own host command.
CLI
boxel run-command <command-specifier> --realm <realm-url> [--input '<json>'] [--json]
<command-specifier>— the module path of the command (e.g.@cardstack/boxel-host/commands/get-card-type-schema/default).--realm— the realm URL the command runs against. Required.--input— JSON string passed as the command's input. Optional; some commands take no input. Keys map to the input card's field names. AlinksTofield is given the target card's ID string, and alinksToManyfield an array of ID strings — the host resolves each ID to the actual card before running the command.--json— emit the raw response instead of the formatted summary.
Example
boxel run-command @cardstack/boxel-host/commands/get-card-type-schema/default \
--realm http://localhost:4201/my-realm/ \
--input '{"codeRef":{"module":"http://localhost:4201/my-realm/sticky-note","name":"StickyNote"}}'
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 · 92 lines · 75 tokens per session scan A 5b5fa8b0c140
boxel-command is a skill published in the GitHub repository cardstack/boxel (27 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 1,535 once invoked, about $0.0003 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.