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/omrikais/cctally/dbgit clone --depth 1 https://github.com/omrikais/cctallyWhat 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.00000 | $0.09884 |
| Opus 5 | $0.00000 | $0.04942 |
| Sonnet 5 | $0.00000 | $0.01977 |
| Haiku 4.5 | $0.00000 | $0.00988 |
Grade A, and why
db 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 — 689 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cctally db
Migration / DB-management subcommand. Twelve actions: status, skip,
unskip, rebuild, rederive, journal-repair, recover, repair,
backup, checkpoint, prune, and vacuum.
Synopsis
cctally db status [--json]
cctally db skip <migration-name> [--reason "<text>"]
cctally db unskip <migration-name>
cctally db rebuild --db stats [--json]
cctally db rederive --family claude-usage [--yes] [--json]
cctally db journal-repair [--violation <fingerprint> ...] [--yes] [--json]
cctally db recover --db cache [--yes] # --db stats is retired (see below)
cctally db repair --db stats --yes
cctally db backup --db {cache,stats} [--output <path>]
cctally db checkpoint [--db {cache,conversations,stats}] [--json]
cctally db prune [--yes] [--include-backups] [--json]
cctally db vacuum [--db {cache,conversations,stats,all}]
Description
cctally runs schema migrations on open_cache_db() (cache.db) and
open_conversations_db() (conversations.db) via a small in-process
framework. Migrations are numbered (001_…, 002_…), per-DB, registered
via @cache_migration / @conversations_migration decorators in
bin/cctally. The db subcommand surfaces this state and offers a manual
poison-pill escape.
stats.db is different since the journal redesign (§7.1): it is a
disposable index materialized from the append-only journal, stamped at a
single STATS_INDEX_EPOCH (1004) rather than versioned by migrations.
Its 13-migration legacy registry is frozen — no new stats migration is
ever written; a schema change bumps the epoch, and any version mismatch
self-heals by rebuild (db rebuild --db stats), never by trim-and-revert.
db status still lists the frozen stats registry for provenance.
Spec: docs/superpowers/specs/2026-05-06-migration-framework-design.md,
docs/superpowers/specs/2026-07-22-db-journal-redesign-design.md.
cctally db status
Renders applied / pending / failed / skipped state for every migration in both DBs.
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 · 689 lines · 0 tokens per session scan A 79d899b6e500
db is a command published in the GitHub repository omrikais/cctally (5 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 9,884 tokens. 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.