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 commands/midnightdarling/collate/statusgit clone --depth 1 https://github.com/MidnightDarling/collateWhat 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.00012 | $0.00341 |
| Opus 5 | $0.00006 | $0.00170 |
| Sonnet 5 | $0.00002 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
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
Report the current pipeline stage and recommended next action for a workspace.
Argument: $ARGUMENTS (workspace path; if omitted, infer from the most recently modified *.ocr/ in the current directory).
Read status
Read <workspace>/_internal/_pipeline_status.json. It contains at minimum:
stage: prep-scan / ocr-run / proofread / apply-review / diff-review / done / failedstatus: ok / awaiting_agent_review / errornext_step: guidance for the next actionfiles_preserved: retained audit artifacts
Artifact checklist
Verify presence of key deliverables (✓ present / ✗ missing):
<ws>/raw.md<ws>/meta.json<ws>/review/raw.review.md<ws>/final.md<ws>/previews/diff-review.html<ws>/review/diff-summary.md<ws>/output/*_final.docx<ws>/output/*_wechat.html<ws>/README.md(workspace entry point)
Report format
Workspace: <abs path>
Stage: <stage> / <status>
Next: <next_step>
Present:
- ...
Missing:
- ...
Suggested command: <one or two slash commands>
If status=error, include the error summary, cause, and next_step. Guide the user toward diagnosis; do not attempt to auto-fix.
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 · 50 lines · 12 tokens per session scan A 895554792d2e
status is a command published in the GitHub repository MidnightDarling/collate (6 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 341 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 commands, from other repositories
t800-start
Единая команда. Создание rules, skills, commands, subagents, hooks — для плагина, текущего проекта или глобально.
t800-fix
Зачем: узкая правка существующих agents / skills / commands / rules / hooks по pack — без полного DEEP /t800-start.
t800-doctor
Зачем: быстрый scripts-only отчёт: версия, profile, memory, STATE, counts, alwaysApply, последние audits — без narrative-агента по умолчанию.
t800-onboard
Для чата с новичками. Показывает, что настроено в Cursor (global + local), и что умеет отдел T-800.
t800-bootstrap
Запускайте один раз при установке плагина или для новичка в чате.
t-800-factory
Обязательно вызови субагента через Task(t-800-factory).