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/initgit clone --depth 1 https://github.com/Not-Diamond/self-careWhat 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.00010 | $0.01817 |
| Opus 5 | $0.00005 | $0.00908 |
| Sonnet 5 | $0.00002 | $0.00363 |
| Haiku 4.5 | $0.00001 | $0.00182 |
Grade A, and why
init 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.
How it starts
The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-Care Init
Set up Self-Care for this project. Configures the trace source (LangSmith or LangFuse), validates credentials, and creates the local directory structure.
Step 1: Determine Config Path
The config lives in the project-local .self-care/ directory:
CONFIG_PATH=".self-care/config.json"
Store CONFIG_PATH for use throughout.
Step 2: Check Existing Config
Read $CONFIG_PATH. If the file exists and contains valid JSON:
Output the current configuration:
Self-Care is already configured:
Source: <source>
Project: <project name if applicable>
Initialized: <initialized_at>
Then ask via AskUserQuestion:
Would you like to reconfigure? (yes/no)
If "no": stop here. If "yes" or if no config exists: continue.
Step 3: Choose Trace Source
Ask via AskUserQuestion:
Where are your agent traces?
1. LangSmith
2. LangFuse
Store the choice as source.
Step 4: Validate Credentials
If source = LangSmith:
Check that LANGSMITH_API_KEY is set:
"${CLAUDE_PLUGIN_ROOT}/scripts/check-env.sh" LANGSMITH_API_KEY
If the output shows LANGSMITH_API_KEY=unset, output the following and stop:
✗ LANGSMITH_API_KEY not set.
Add it to your .env file or export it in your shell:
export LANGSMITH_API_KEY=lsv2_pt_...
If set, fetch available projects (source .env again since each Bash call is a fresh shell):
if [ -f .env ]; then set -a && source .env && set +a; fi
node "${CLAUDE_PLUGIN_ROOT}/lib/validate-creds.mjs" --source langsmith --list-projects
Parse the JSON output. The response contains { projects: [{ name, run_count }] }.
If the command exits non-zero, output the stderr message and stop.
If projects were fetched successfully, present them via AskUserQuestion as a numbered list:
Select your LangSmith project:
1. <project_name> (<run_count> traces)
2. <project_name> (<run_count> traces)
...
Include all fetched projects as numbered options. The user selects one.
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 · 253 lines · 10 tokens per session scan A 4b1a706d58c7
init is a command published in the GitHub repository Not-Diamond/self-care (28 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 1,817 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
project-hierarchy-check
Use this command before changing organisation, project, or database config behavior.
coder-eval-implement-plan
Implement an approved codereval plan phase by phase with risk-scaled per-phase review, then a final code review.
lab
Advanced history search and analysis for AI coding agent sessions.
scrim
Cost and tool-output report. Retrieve a stashed original with scrim get.
speckit.git.validate
Validate current branch follows feature branch naming conventions.
checklist
Generate a custom checklist for the current feature based on user requirements.