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/status)<a href="https://agentmods.dev/skills/raisedadead/claude-code-plugins/status"><img src="https://agentmods.dev/badge/skills/raisedadead/claude-code-plugins/status/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/status"><img src="https://agentmods.dev/badge/skills/raisedadead/claude-code-plugins/status.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.00064 | $0.02440 |
| Opus 5.5 | $0.00026 | $0.00976 |
| Sonnet 5.5 | $0.00013 | $0.00488 |
| Haiku 4.5 | $0.00006 | $0.00244 |
Grade B, and why
status scanned grade B with 1 finding 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 7d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
1. **transcripts** — grep `~/.claude/projects/<project>/*.jsonl` from the last `${DS_RECOVER_DAYS:-3}` days for the most recent non-sidechain user turns plus the last assistant summary. Header `## Recovered (transcripts) How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ds:status — the dossier driver (sit-rep)
Read-only on files; mutations route through Bash helpers. The sit-rep writes only the INDEX regen and the TaskList hydration; pause and resume (step 1a) write the ledger on request. Step 6 lists both.
Steps
1. Locate
.scratchpad/INDEX.md— missing → runds regen-indexto build it.- Enumerate ALL rows with
state=live. Current dossier = the first (most-recent).state=pausedrows are listed separately, outside the live set. - The paused set reaches the report as its own
PAUSEDline in step 5, printed on every full sit-rep —(none)when the set is empty. The LIGHT path exits at step 1 and never reaches it, which is correct: LIGHT runs where there is no.scratchpad/dossier/to hold a paused wave. A paused wave that no line names is a wave nobody decides about.
No .scratchpad/dossier/ in cwd → LIGHT sit-rep, the small-work path with no ceremony:
git status -sb+git log --oneline -${DS_LIGHT_LOG:-5}for working state (skip git cleanly outside a repo).$DS_HEALTH_CMDwhen set: run it and fold its output in (the operator wires a repo/rig health check; unset stays portable).- One block:
LIGHT (no dossier): <branch> · <ahead/behind> · <N> dirty · last: <subject>, then suggestds:new "<goal>"when the work meets the start rule: it spans more than one session, touches more than 5 files, or needs an operator step.
Exit 0 after the light sit-rep.
1a. Consolidation check
Warn (advisory, never blocking) when the tree needs tidying:
- >1 live dossier (Vm.12): print a CONSOLIDATE block listing each live slug and its §S-tail age, then suggest picking the current one and pausing or closing the rest.
- stale-live (Vm.13): any live dossier whose last §S entry is older than
${DS_STALE_LIVE_DAYS:-14}days → suggest pause ords:close --abandon. - drift (Vm.15): an INDEX carrying a
<!-- drift:N slugs:... -->trailer (any dossier rendereddrift!— header/location/§Z disagreement, the sealed-zombie class) gets a DRIFT block naming each drift slug and its likely cause, then a route: a§Z-closed drift auto-heals on the next SessionStart (session-start runsds reconcile); anything else is operator-resolved — finish the close (rerunds close <wave>) or correct the header throughds header-state, which is the supported writer (the dossier mod's header guard denies a non-canonical token written any other way). Runcli/ds ds-check .scratchpadfor the deterministic list.
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.
- 7d ago Changed · -2 lines 0b8c557d02b4
- 14d ago Changed c49e8a671d9e
- 18d ago Changed · -8 lines dd2373af7faa
- 1mo ago First seen · 142 lines · 64 tokens per session scan B 2d88ef579134
status is a skill published in the GitHub repository raisedadead/claude-code-plugins (3 stars, last pushed today), licensed ISC. It adds 64 tokens to every session and 2,440 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…