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/catalog-pairing/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/catalog-pairing)<a href="https://agentmods.dev/skills/cardstack/boxel/catalog-pairing"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/catalog-pairing/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/catalog-pairing"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/catalog-pairing.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.00326 | $0.03575 |
| Opus 5.5 | $0.00130 | $0.01430 |
| Sonnet 5.5 | $0.00065 | $0.00715 |
| Haiku 4.5 | $0.00033 | $0.00358 |
Grade A, and why
catalog-pairing 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pairing boxel and boxel-catalog pull requests
This repo's PreToolUse hook (.claude/hooks/require-skill.mjs) refuses to open or edit a boxel-catalog pull request, or to write a Merges before: / Merges after: line into any pull request's description, through gh pr or the GitHub MCP tools, until the session or subagent has loaded this skill.
boxel-catalog's cards import boxel (host tools, @cardstack/base, runtime types), and boxel's tests use some catalog definitions. So a change in one repository can need a change in the other, and the two pull requests have to be checked together and merged in the right order. Each pull request says which pull request it pairs with in its description, and the checks in both repositories read that.
When a change needs a pair
- A boxel change the catalog has to follow. Renaming or removing a host tool or command (
@cardstack/boxel-host/tools/*), a base export, a field or a type that catalog cards import, or tightening a type or lint rule they trip. The boxel pull request merges first, and the catalog pull request that adapts the cards merges right after it. The boxel pull request also pins the catalog pull request's head (see The pin covers the whole catalog). - A catalog change boxel's tests need. A new or changed definition in the catalog test subset (the
catalog-test-subsetskill). The catalog pull request merges first, and the boxel pull request that re-pins and tests it merges after. - Both at once: the three-PR flow. A catalog definition that needs new platform code, and whose boxel tests need the new definition. Platform pull request A merges, then catalog pull request C, then boxel pull request B, which re-pins and tests. C is tested against B's head, and that head needs A's platform code. So B carries A by merging A's branch into it and following A until A merges. B may target
mainwith A merged in, or be stacked on A (below) and be retargeted tomainonce A merges. Stacked, B can't pass the catalog-main gate as aMerges beforeside until it's retargeted, since merging it lands it on A's branch, notmain.
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 · 88 lines · 326 tokens per session scan A 1c8c16428612
catalog-pairing is a skill published in the GitHub repository cardstack/boxel (27 stars, last pushed today), licensed MIT. It adds 326 tokens to every session and 3,575 once invoked, about $0.0013 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
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.