Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add raisedadead/claude-code-plugins/plugin install dossierWrote 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/raisedadead/claude-code-plugins/check)<a href="https://agentmods.dev/skills/raisedadead/claude-code-plugins/check"><img src="https://agentmods.dev/badge/skills/raisedadead/claude-code-plugins/check/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/raisedadead/claude-code-plugins/check"><img src="https://agentmods.dev/badge/skills/raisedadead/claude-code-plugins/check.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.00059 | $0.02070 |
| Opus 5.5 | $0.00024 | $0.00828 |
| Sonnet 5.5 | $0.00012 | $0.00414 |
| Haiku 4.5 | $0.00006 | $0.00207 |
Grade A, and why
check 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 14d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ds:check — drift detector
Validates DOSSIER.md against reality and returns a severity-tagged violation list. It changes no DOSSIER.md content and no repo. Two derived paths are written: INDEX.md, which ds ds-check regenerates on every run (step 3), and .scratchpad/.verify-cache/, which ds verify-sweep populates at step 2a. Both are caches rebuilt from source, never source themselves — the carve-out step 6 states.
Steps
1. Locate
Live dossier per ds:status step 1. --all adds archived dossiers as a sanity sweep.
2. Plan scout dispatch
One scout mission per §X repo, independent and parallel.
Mission template (per scout):
You are a dossier-scout. Read-only.
Dossier: <path-to-DOSSIER.md> (full file pasted below)
Repo to scan: <repo-path>
Headings are dual-spelled and the pasted file may use either. A ds:new
scaffold writes the plain names (`## Invariants`, `## Tasks`, `## Repos`);
older files write the sigils (`## §V`, `## §T`, `## §X`). The §-names below
are the section, not the literal heading — match whichever the file carries.
Tasks:
1. For each Invariants (§V) row with `check` = shell predicate: run the predicate, report PASS/FAIL.
2. For each Invariants (§V) row with `check` = test name: locate test in <repo-path>, run if executable, report PASS/FAIL/MISSING.
3. For each Tasks (§T) row with state=`x` + `cite=<sha>`: verify <sha> exists in <repo-path> git log. Report VALID/MISSING.
4. Refresh Repos (§X) for <repo>: git status -sb, ahead-count, latest tag, push state. Report current values; do NOT modify DOSSIER.md.
Output: terse pipe-table. One row per finding.
<paste DOSSIER.md here>
Spawn one dossier-scout per repo, in parallel, via the Agent tool with subagent_type: dossier:dossier-scout.
§X repos > 2 and Workflow present → route the same missions through the §workflow fan-out (${CLAUDE_PLUGIN_ROOT}/ADAPTERS.md): schema-validated rows, budget-gated width, crash-resumable. Otherwise the Agent spawns above.
2a. Verify-layer sweep (existing content)
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.
- 14d ago Changed c0b6c860c5ff
- 18d ago Changed · -5 lines 93e55b702f9e
- 1mo ago First seen · 140 lines · 59 tokens per session scan A 11500b73f204
check is a skill published in the GitHub repository raisedadead/claude-code-plugins (3 stars, last pushed today), licensed ISC. It adds 59 tokens to every session and 2,070 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-08-31.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…