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/protomated/protomated-plugins-official/log-timegit clone --depth 1 https://github.com/protomated/protomated-plugins-officialWhat 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.00010 | $0.00540 |
| Opus 5 | $0.00005 | $0.00270 |
| Sonnet 5 | $0.00002 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
log-time 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/legal-billing:log-time — Log Billable Time
Guide the attorney through a complete time entry. Collect missing fields conversationally — don't present a form all at once.
Invocation
/legal-billing:log-time $ARGUMENTS
Parse any details the attorney already provided in $ARGUMENTS (client name, hours, rate, matter name, description). Only ask for what's missing.
Workflow
Step 0 — Confirm setup first: Call connect_google with check_only: true. If not connected, stop and tell the attorney to say "connect Google" — do not collect any fields yet. If connected, proceed; if the first data call below returns "No Google Sheet configured yet", stop and ask whether to create a new sheet from the template (create_billing_sheet, only after they confirm) or connect an existing one (set_spreadsheet_url). Only continue once both are confirmed. If you call create_billing_sheet, always paste the full sheet URL from its result into your reply — do not just say "sheet created."
Step 1 — Collect required fields (ask only for what's missing):
- Client name — exact spelling matters; repeat it back for confirmation if new
- Hours worked — decimal format (e.g., 1.5 for 1 hour 30 min); never 0 or negative
- Hourly rate — dollars per hour, no $ sign; ask if not provided, never guess
- Date — default to today if not specified
- Matter name — optional but recommended for multi-matter clients
- Matter type — if missing, ask using exactly this list: Litigation, Family Law, Estate, Criminal, Corporate, Immigration, Real Estate, Small Business
- Description of work — brief; suggest one if the attorney is vague ("Client consultation")
Step 2 — Confirm before logging: "Logging: [hours] hours for [client] on [matter] at $[rate]/hr ([description]) — [date]. Go ahead?"
Wait for confirmation.
Step 3 — Call log_time, then report:
"✅ Logged: [hours] hours for [client] ([matter]) at $[rate]/hr — $[total] fee. Status: Unbilled.
⚠️ Not legal advice — review before sending to client."
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 · 39 lines · 10 tokens per session scan A 3abd71e671d6
log-time is a command published in the GitHub repository protomated/protomated-plugins-official (2 stars, last pushed 22d ago), licensed Apache-2.0. It adds 10 tokens to every session and 540 once invoked, about $0.0001 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.