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/hook-tickgit clone --depth 1 https://github.com/omrikais/cctallyWrote 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/omrikais/cctally/hook-tick)<a href="https://agentmods.dev/commands/omrikais/cctally/hook-tick"><img src="https://agentmods.dev/badge/commands/omrikais/cctally/hook-tick.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 | $0.00000 | $0.00588 |
| Opus 5 | $0.00000 | $0.00294 |
| Sonnet 5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
hook-tick 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 3d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cctally hook-tick
Internal — invoked automatically by Claude Code hooks.
Users normally don't run this directly. Hidden from cctally --help.
What it does
On every assistant-message boundary (PostToolBatch, Stop, SubagentStop):
- Reads the CC hook payload from stdin (JSON:
hook_event_name,session_id,transcript_path,cwd). - Detaches stdout/stderr to
~/.local/share/cctally/logs/hook-tick.log. - Tail-ingests new JSONL entries into the local SQLite cache.
- If
~/.local/share/cctally/hook-tick.last-fetchis older than the throttle threshold (default 30s), refreshes 7-day / 5-hour rate limits from the Anthropic OAuth usage API and writes via the samerecord-usagepath. - Writes one log line. Returns 0 unconditionally.
Useful flags (manual / debugging)
--explain— synchronous, prints decision tree to stdout, exits informative code.--no-oauth— skip OAuth refresh entirely (local sync only).--throttle-seconds N— override the 30s default.--event NAME— override the event name written to the log line (rare).
Log format
<UTC ISO ts> event=<E> session=<sid8> ingested=<N> oauth=<status> dur_ms=<D>
oauth= values:
ok(7d=N,5h=M)/ok(7d=N)— fetched successfully (5h optional)throttled(age=Ns)— last fetch was less than the throttle threshold agoskipped-no-oauth—--no-oauthflag setskipped-no-token— no Claude OAuth token found in keychain or credentials fileerr(network)/err(parse)— fetch or parse failederr(record-usage=K)/err(record-usage=exc)—record-usagereturned exit code K or raisederr(internal:<TypeName>)— uncaught exception class within the hook (rare; signals a bug)
Rotation: when the log file exceeds 1 MB, it's atomic-renamed to
hook-tick.log.1 (single-generation; older .1 is overwritten).
See also
setup— installs the hook entries that firehook-tickrefresh-usage— manual variant that busts the status-line cacherecord-usage— direct status-line integration (alternative to hooks)
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.
- 3d ago First seen · 50 lines · 0 tokens per session scan A b2370640db07
hook-tick is a command published in the GitHub repository omrikais/cctally (5 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 588 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.