Borrowing it
Nothing to install: this file belongs to cardstack/boxel. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/cardstack/boxel/main/.claude/skills/operations-diagnosis/SKILL.mdgit 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/operations-diagnosis)<a href="https://agentmods.dev/skills/cardstack/boxel/operations-diagnosis"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/operations-diagnosis/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/operations-diagnosis"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/operations-diagnosis.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.00000 | $0.12424 |
| Opus 5.5 | $0.00000 | $0.04970 |
| Sonnet 5.5 | $0.00000 | $0.02485 |
| Haiku 4.5 | $0.00000 | $0.01242 |
Grade A, and why
operations-diagnosis 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 — 429 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operations and policy diagnosis
A realm's ACL answers "may this caller read the realm, or write it?". A realm's policy — the RealmPolicy card its realm.json policy key names — widens that answer for a caller the ACL declined, one grant at a time. The gate (packages/runtime-common/card-operations/gate.ts) judges every invocation such a caller makes; the search lane (card-operations/policy-query.ts) composes the policy's query grants into every search such a caller runs; the realm keeps a compiled copy of the policy card (RealmPolicyCache in card-operations/policy.ts).
Each of those leaves a record, and this skill is about reading them to answer an operator's question: why did this user get refused, which realm's policy is broken, is the policy reached more than it should be, which grant admits too much. A realm owner asking about one (actor, target, operation) triple has a better tool than logs — see When explain is the better tool. For what a policy costs (evaluationMs, predicateMs, compile durations) read policy-performance; this skill does not restate it.
Where the lines come from
Two places, and they are read differently.
boxel:operations — one flat JSON object per line, channel: "boxel:operations", the same | json convention as boxel:client-perf and boxel:search-shape. Every shape is defined in card-operations/telemetry.ts; its comments are the authority on what a field means. Seven shapes share the channel, told apart by kind:
kind |
one line per | emitted from |
|---|---|---|
| (absent) | execution of an operation built on transform: committed, or refused while staging |
executors.ts, coordinator.ts |
policy-decision |
gate decision for a caller the ACL declined; for a write left to the lock, also the lock's | gate.ts |
policy-search-scope |
realm a search consulted only through its policy | policy-query.ts |
policy-compile |
read of a realm's policy card by its cache — a compile or a revalidation | policy.ts |
policy-snapshot-read |
evaluation of a predicate annotated snapshot: true (judged against the index row) |
gate.ts |
capability-check |
successful POST <realm>/_capabilities request |
Realm#handleCapabilities in realm.ts |
anonymous-request |
request from a caller who isn't signed in that reached a realm's anonymous admission | anonymous-admission.ts |
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 · 429 lines · 0 tokens per session scan A bb69adee4a98
operations-diagnosis is a skill published in the GitHub repository cardstack/boxel (27 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 12,424 tokens. 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.