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.
git clone --depth 1 https://github.com/zircote/subcogWrote 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/zircote/subcog/sync)<a href="https://agentmods.dev/commands/zircote/subcog/sync"><img src="https://agentmods.dev/badge/commands/zircote/subcog/sync/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/zircote/subcog/sync"><img src="https://agentmods.dev/badge/commands/zircote/subcog/sync.svg" alt="Reviewed on agentmods" width="80" 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.00013 | $0.00409 |
| Opus 5.5 | $0.00005 | $0.00164 |
| Sonnet 5.5 | $0.00003 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
sync 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 1mo 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
/subcog:sync
Deprecated: With the migration to SQLite as authoritative storage, remote sync is no longer supported. This command returns no-op results for all operations. Memories are now stored locally in SQLite with project/branch/path faceting.
Usage
/subcog:sync # No-op (returns empty stats)
/subcog:sync --push # No-op (returns empty stats)
/subcog:sync --fetch # No-op (returns empty stats)
/subcog:sync --full # No-op (returns empty stats)
Arguments
Current Architecture
For Team Sharing: If you need to share memories across team members, consider:
- Using PostgreSQL backend with shared connection string
- Exporting/importing memories via
subcog export/subcog import
Examples
Alternative - Check database status:
subcog status
Shows SQLite database path and memory count.
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.
- 1mo ago First seen · 59 lines · 13 tokens per session scan A 378316754bd2
sync is a command published in the GitHub repository zircote/subcog (29 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 409 once invoked, about $0.0001 per session on Opus 5.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
address-pr-feedback
Systematically address PR review comments. Fetches all threads, categorizes by status (acknowledged, silently fixed, unaddressed), and guides user through posting replies and implementing fixes with explicit approval.
advanced-code-review-context
Advanced Code Review Phase 2: Context Analysis - load previous reviews, PR history, declined items.
create-issue
Create a GitHub issue with proper template discovery and population.
create-pr
Create a pull request with proper template discovery and population.
pr-dance
Loop a PR through CI and bot review until merge-ready. Use when user says '/pr-dance', 'do the PR dance', or finishing-a-development-branch dispatches option 3.
simplify-transform
Apply verified simplifications with user approval. Part of simplify- family.