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/remotecto/claude-code-timelog/helpgit clone --depth 1 https://github.com/RemoteCTO/claude-code-timelogWhat 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.00009 | $0.00383 |
| Opus 5 | $0.00005 | $0.00192 |
| Sonnet 5 | $0.00002 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
help 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.
What it actually says
Timelog Commands
Available Commands
| Command | Description |
|---|---|
/timelog:report |
Generate time reports |
/timelog:backfill |
Import existing sessions |
/timelog:help |
Show this help |
Report Examples
/timelog:report --week --by-project
/timelog:report --month --by-ticket
/timelog:report --timesheet
/timelog:report --from 2026-02-01 --to 2026-02-14
/timelog:report --project my-app --by-ticket
/timelog:report --json
Report Flags
| Flag | Description |
|---|---|
--week |
This week (default) |
--month |
This month |
--by-project |
Group by project (default) |
--by-ticket |
Group by ticket |
--by-model |
Group by model |
--by-day |
Group by day |
--timesheet |
Project → ticket breakdown |
--from DATE |
Start (YYYY-MM-DD) |
--to DATE |
End (YYYY-MM-DD) |
--project NAME |
Filter by project |
--ticket ID |
Filter by ticket |
--json |
JSON output |
Configuration
Edit ${CLAUDE_TIMELOG_DIR}/config.json:
{
"breakThreshold": 1800,
"ticketPatterns": ["([A-Z][A-Z0-9]+-\\d+)"],
"projectSource": "git-root"
}
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 · 57 lines · 9 tokens per session scan A 9736b1dc07b2
help is a command published in the GitHub repository RemoteCTO/claude-code-timelog (7 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 9 tokens to every session and 383 once invoked, about $0.0000 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
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.