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 agentmods add skills/defiect/deep-research-plugin/statusnpx skills add Defiect/deep-research-plugin --skill statusgit clone --depth 1 https://github.com/Defiect/deep-research-pluginWhat 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 | $0.00028 | $0.00288 |
| Opus 5 | $0.00014 | $0.00144 |
| Sonnet 5 | $0.00006 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
status 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 2d 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.
What it actually says
Check the status of the most recent deep research run.
Instructions
- Find the latest run directory under
.deep-research/runs/(sort by directory name, most recent first). - Read
run.jsonfor the run metadata and current status. - Count entries in
sources.jsonl,claims.jsonl, andevidence.jsonl. - List any notes files in the
notes/directory. - Check if
report.mdexists and has content. - Run a quick audit:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/dr_audit.py --mode full --run-dir <run_dir>
Output
Provide a concise status summary:
- Run ID: the run identifier
- Topic: the research question
- Status: current phase (planning/scouting/analyzing/synthesizing/complete)
- Sources: count and breakdown by type
- Claims: count and breakdown by importance and status
- Evidence: edge count
- Notes: number of source notes written
- Report: exists/empty/missing
- Audit: pass/fail with failure details if any
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.
- 2d ago First seen · 29 lines · 28 tokens per session scan A 8b3ebe0d0712
status is a skill published in the GitHub repository Defiect/deep-research-plugin (2 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 288 once invoked, about $0.0001 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.