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-statusgit 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-status)<a href="https://agentmods.dev/commands/not-diamond/self-care/autosync-status"><img src="https://agentmods.dev/badge/commands/not-diamond/self-care/autosync-status.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.1 | $0.00009 | $0.00343 |
| Opus 5 | $0.00005 | $0.00171 |
| Sonnet 5 | $0.00002 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
autosync-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 6d 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
Self-Care Autosync Status
Display the current autosync status from .self-care/autosync.json plus the global project runtime memory under .self-care/autosync/.
Step 1: Define Paths
CONFIG_PATH=".self-care/config.json"
STATE_PATH=".self-care/autosync.json"
Step 2: Load Status
Run:
node "${CLAUDE_PLUGIN_ROOT}/lib/autosync.mjs" status --config "$CONFIG_PATH" --state "$STATE_PATH"
Parse the JSON output and display:
Self-Care Autosync
Enabled: <true|false>
Source: <source or unconfigured>
Project: <project or n/a>
Host: <host if langfuse, otherwise n/a>
Interval: every <poll_interval_minutes> minute(s)
Sampling rate: <sampling_rate>
Last sync: <last_sync_at or never>
Last sync count: <last_sync_count>
Pending traces: <pending_count>
Next sync: <next_sync_at or n/a>
Consecutive errors: <consecutive_errors>
Last error: <last_error or none>
Task ID: <loop_task_id or none>
Config file: .self-care/autosync.json
Runtime: .self-care/autosync/
If scope_changed is true, add one extra line:
Note: the connected source or project changed since autosync was last enabled.
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.
- 6d ago First seen · 53 lines · 9 tokens per session scan A cd4b279a610c
autosync-status 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 343 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.