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/telemetrygit 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.00931 |
| Opus 5 | $0.00000 | $0.00465 |
| Sonnet 5 | $0.00000 | $0.00186 |
| Haiku 4.5 | $0.00000 | $0.00093 |
Grade A, and why
telemetry 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
telemetry
Inspect and control cctally's anonymous, opt-out install-count telemetry. cctally sends, at most once a day, a minimal beat — a one-way month-rotating token (never your install id), the client version, and a coarse OS family (macos/linux/windows/other). No username, path, or session content is ever sent; no IP is included in the payload or retained by the server (Cloudflare necessarily sees the source IP to route the request — see ../telemetry.md for the honest threat model).
This page is the command reference. For the full privacy story — what is sent, what is never collected, how the token's cross-month unlinkability works, retention, and the honest threat model — see ../telemetry.md.
Synopsis
cctally telemetry [on | off | reset] [--json]
Actions
| Action | Effect |
|---|---|
| (none) | Show the current state: enabled/disabled + the resolved precedence reason, what gets sent (with the resolved version and OS family), the token that would be used this month, and the opt-out surfaces. Read-only — it previews the current month's token from an existing install id without ever minting one, and shows (not yet armed) when no id exists yet. |
on |
Enable telemetry (sets telemetry.enabled = true). Thin wrapper over cctally config set telemetry.enabled true. |
off |
Disable telemetry (sets telemetry.enabled = false). Thin wrapper over cctally config set telemetry.enabled false. |
reset |
Discard the local install_id and mint a fresh one, rotating your identity for future months. |
Options
| Flag | Effect |
|---|---|
--json |
Emit the status as JSON (status output only — has no effect with on/off/reset). |
Resolved state and precedence
The bare-status view reports whether telemetry is enabled and why, resolved by a side-effect-free predicate. First match wins:
CCTALLY_DISABLE_TELEMETRYset (truthy) → disabled, reasonenv-disabled.DO_NOT_TRACKset (truthy) → disabled, reasondo-not-track.- Running from a dev checkout → disabled, reason
dev-checkout. telemetry.enabled = falsein config → disabled, reasonconfig-disabled.- Otherwise → enabled, reason
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.
- 2d ago First seen · 77 lines · 0 tokens per session scan A 2732f8b5e09d
telemetry 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 931 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.