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.
git clone --depth 1 https://github.com/WYRE-AI/msp-claude-pluginsWrote 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/wyre-ai/msp-claude-plugins/log-time)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/log-time"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/log-time/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/log-time"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/log-time.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00008 | $0.01783 |
| Opus 5.5 | $0.00003 | $0.00713 |
| Sonnet 5.5 | $0.00002 | $0.00357 |
| Haiku 4.5 | $0.00001 | $0.00178 |
Grade A, and why
log-time scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X GET "https://app.atera.com/api/v3/tickets/{ticket_id}" \ How it starts
The opening of the file, as written. The whole thing — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Log Time on Atera Ticket
Log work hours on an Atera ticket for billing and tracking purposes.
Prerequisites
- Valid Atera API key configured
- Ticket must exist in Atera
- User must have time entry permissions
Steps
-
Validate ticket exists
curl -s -X GET "https://app.atera.com/api/v3/tickets/{ticket_id}" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Accept: application/json"- Verify ticket exists
- Capture ticket details for confirmation
- Check if ticket is closed (warn user)
-
Validate time entry parameters
- Validate hours is a positive decimal
- Parse date if provided, default to today
- Set billable default to true if not specified
-
Create time entry
curl -s -X POST "https://app.atera.com/api/v3/tickets/{ticket_id}/workhours" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "Hours": <hours>, "Notes": "<notes>", "Date": "<date>", "Billable": <billable>, "HourlyRate": <hourly_rate> }' -
Return confirmation
- Time entry ID
- Ticket summary
- Hours logged
- Billable status
- Running total for ticket
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| ticket_id | integer | Yes | - | The ticket ID to log time against |
| hours | decimal | Yes | - | Hours worked (e.g., 0.5, 1.25, 2) |
| notes | string | No | - | Description of work performed |
| date | date | No | today | Date of work (YYYY-MM-DD) |
| billable | boolean | No | true | Mark time as billable |
| hourly_rate | decimal | No | - | Override default hourly rate |
Examples
Basic Time Entry
/log-time 12345 1.5
Time with Notes
/log-time 12345 1.5 --notes "Troubleshot network connectivity issue"
Non-Billable Time
/log-time 12345 0.5 --billable false --notes "Internal documentation"
Previous Day Entry
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.
- 1mo ago First seen · 312 lines · 8 tokens per session scan A 8f1fb1fb2758
log-time is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (51 stars, last pushed today), licensed Apache-2.0. It adds 8 tokens to every session and 1,783 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
project
A command-style entry point for initializing a project with an interview, custom agents, skill workflows, and project instruction files. It also supports update, evolution, and diagnostic modes.
factory
Run one pass of the ticket queue — scan the tracker for human-authorized tickets, claim one, and route it to the right workflow (spec a raw ticket, groom the backlog, hunt a bug, or build an approved spec in its own worktree via /sonu:build). You are the trigger; there is no daemon. Never merges and never authorizes…
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.
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.