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/not-diamond/self-care/rungit clone --depth 1 https://github.com/Not-Diamond/self-careWrote 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/commands/not-diamond/self-care/run)<a href="https://agentmods.dev/commands/not-diamond/self-care/run"><img src="https://agentmods.dev/badge/commands/not-diamond/self-care/run.svg" alt="Measured on agentmods" 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 | $0.00019 | $0.06749 |
| Opus 5 | $0.00010 | $0.03374 |
| Sonnet 5 | $0.00004 | $0.01350 |
| Haiku 4.5 | $0.00002 | $0.00675 |
Grade A, and why
run 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 3d 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 — 729 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Pipeline
Run the full Self-Care triage pipeline on the provided trace file. Supports both OTEL (JSON) and Claude Code (JSONL) formats. This orchestrates 6 stages sequentially: validation, analysis, reporting, finding review, output lists, and feedback (only if you've opted in).
Stage 0a: Analytics Consent Check
Before running the pipeline, check if the user has consented to analytics collection.
Read the config file at .self-care/config.json using the Read tool.
- If the file exists and contains valid JSON with
analytics.enabledset totrueorfalse: consent is already recorded. Skip to Stage 0b. - If the file does not exist, or exists but has no
analyticskey: prompt for consent.
Prompt for consent using AskUserQuestion:
- question: "Self-Care can collect anonymous usage analytics to help improve the tool. This includes: command usage frequency, case types detected (not trace content), and error rates. No trace data, file contents, or personally identifiable information is collected. Would you like to enable analytics?"
- header: "Analytics"
- options:
{ "label": "Enable analytics", "description": "Help improve Self-Care with anonymous usage data" }{ "label": "Disable analytics", "description": "Opt out of usage analytics" }
Save the config:
- Get timestamp:
date -u +"%Y-%m-%dT%H:%M:%SZ" - Ensure the config directories exist:
mkdir -p .self-care/traces .self-care/reports - Read existing
.self-care/config.jsonto preserve other settings (e.g.source,langsmith). Merge theanalyticskey into the existing object and write it back:{ "...existing keys preserved...", "analytics": { "enabled": <true if "Enable analytics", false otherwise>, "consentTimestamp": "<timestamp>" } }
Stage 0b: Parse Arguments
Parse $ARGUMENTS to extract:
- trace_path: The trace file path — the first quoted string (quotes stripped) or the first whitespace-delimited token. May be empty.
- details: All remaining text after the trace file path (trimmed). May be empty.
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.
- 3d ago First seen · 729 lines · 19 tokens per session scan A 72c69225c250
run is a command published in the GitHub repository Not-Diamond/self-care (28 stars, last pushed 4mo ago), licensed MIT. It adds 19 tokens to every session and 6,749 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-30.
Other commands, from other repositories
coder-eval-implement-plan
Implement an approved codereval plan phase by phase with risk-scaled per-phase review, then a final code review.
doctor
Run TokenJam's health check — config, ingest endpoint, and storage. Equivalent to running tj doctor.
scrim
Cost and tool-output report. Retrieve a stashed original with scrim get.
speckit.git.validate
Validate current branch follows feature branch naming conventions.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.