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/autosync-enablegit 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/autosync-enable)<a href="https://agentmods.dev/commands/not-diamond/self-care/autosync-enable"><img src="https://agentmods.dev/badge/commands/not-diamond/self-care/autosync-enable.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.00009 | $0.01256 |
| Opus 5 | $0.00005 | $0.00628 |
| Sonnet 5 | $0.00002 | $0.00251 |
| Haiku 4.5 | $0.00001 | $0.00126 |
Grade A, and why
autosync-enable 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 4d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Self-Care Autosync Enable
Enable background autosync for this project using Claude Code scheduled tasks.
Use the existing .self-care/config.json as the source of truth for the connected provider. Persist configurable autosync settings in .self-care/autosync.json.
Store runtime state, pending traces, and staged trace files under .self-care/autosync/ via the autosync CLI. Do not write runtime state into .self-care/autosync.json.
Step 1: Define Paths
CONFIG_PATH=".self-care/config.json"
STATE_PATH=".self-care/autosync.json"
AUTOSYNC_CLI="node "${CLAUDE_PLUGIN_ROOT}/lib/autosync.mjs""
PROJECT_NAME=<run `basename "$(pwd)"` and store the result>
TICK_PROMPT="/self-care:autosync-tick $PROJECT_NAME"
Step 2: Ensure Self-Care Is Initialized
Read $CONFIG_PATH.
If the file does not exist or is invalid JSON, stop and output:
✗ Self-Care is not initialized for this project.
Run /self-care:init first, then retry /self-care:autosync-enable.
Step 3: Load Current Autosync Settings
Run:
node "${CLAUDE_PLUGIN_ROOT}/lib/autosync.mjs" status --config "$CONFIG_PATH" --state "$STATE_PATH"
Parse the JSON output and store:
poll_interval_minutessampling_rateloop_task_idcurrent_scope
Defaults come from the status output if the autosync file does not exist yet.
Step 4: Confirm Or Update Settings
If .self-care/autosync.json already exists, output the current settings and ask via AskUserQuestion:
Autosync is already configured:
Interval: every <poll_interval_minutes> minute(s)
Sampling rate: <sampling_rate>
Would you like to keep these settings or change them?
1. Keep current settings
2. Change settings
If the user chooses to keep the current settings, reuse them as-is.
Set POLL_INTERVAL_MINUTES and SAMPLING_RATE from the values returned in Step 3.
If there is no autosync config yet, or the user chooses to change settings, ask these questions via AskUserQuestion:
- Poll interval:
How often should autosync poll for traces?
1. Every 5 minutes
2. Every 10 minutes
3. Every 30 minutes
4. Every 60 minutes
5. Custom
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.
- 4d ago First seen · 170 lines · 9 tokens per session scan A 6ce9814c90ab
autosync-enable is a command published in the GitHub repository Not-Diamond/self-care (28 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 1,256 once invoked, about $0.0000 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
optimize
Show TokenJam's savings/optimize report — where quota is going and what's recoverable. Equivalent to running tj optimize.
status
Show TokenJam's current status for every tracked agent — token usage, cost today, and active alerts. Equivalent to running tj status.
uninstall
Remove TokenJam's Claude Code integration — unwires the statusline, hooks, and OTel env vars that /onboard set up. Equivalent to running tj uninstall --yes. Does not remove the plugin itself.
doctor
Run TokenJam's health check — config, ingest endpoint, and storage. Equivalent to running tj doctor.
onboard
Set up TokenJam for this Claude Code install — wires the zero-token statusline, the resume-brief SessionStart hook, and local OTel telemetry ingest via the existing tj onboard command. Runs 100% locally, no signup.
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.