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/thethoughtagen/agentsync/initgit clone --depth 1 https://github.com/TheThoughtagen/agentsyncWhat 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.00013 | $0.00289 |
| Opus 5 | $0.00006 | $0.00144 |
| Sonnet 5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
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 yesterday.
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
/aisync:init
Run aisync init to set up the canonical .ai/ directory structure and import existing tool configurations.
Usage
-
Run the command:
aisync init -
Report the results to the user:
- Which AI tools were detected in the project (Claude Code, Cursor, OpenCode)
- Which existing configs were imported into
.ai/(e.g., existingCLAUDE.mdcontent imported into.ai/instructions.md) - What new files and directories were created
-
If
.ai/already exists, warn the user before proceeding:The
.ai/directory already exists. Runningaisync initagain may overwrite imported content. Use/aisync:statusto check current state instead, or pass--forceif you really want to re-initialize.
Notes
- This is typically run once when first adopting aisync in a project.
- Detection looks for
.claude/,.cursor/,.opencode/,CLAUDE.md,AGENTS.md, and similar tool-native files. - After init, run
/aisync:syncto propagate the canonical config back to all tools.
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.
- yesterday First seen · 30 lines · 13 tokens per session scan A e1fa8df73bd1
init is a command published in the GitHub repository TheThoughtagen/agentsync (2 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 289 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
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
read
Read a specific section from an arXiv paper's HTML version (ar5iv.org).
simplify
You are an expert code simplification specialist focused on enhancing code clarity, consistency, and maintainability while preserving exact functionality. Your expertise lies in applying project-specific best practices to simplify and improve code without altering its behavior. You prioritize readable, explicit code…
index
Command "index" from thrashr888/agentkernel, covering commands, quick reference, daily drivers (root level), sandbox lifecycle (sandbox / sb) and ssh (ssh).
snapshots
Save and restore sandbox state. Snapshots capture the full filesystem of a running or stopped sandbox using docker commit.