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/wyre-ai/msp-claude-plugins/schedule-entrygit 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/schedule-entry)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/schedule-entry"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/schedule-entry.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.1 | $0.00010 | $0.02632 |
| Opus 5 | $0.00005 | $0.01316 |
| Sonnet 5 | $0.00002 | $0.00526 |
| Haiku 4.5 | $0.00001 | $0.00263 |
Grade A, and why
schedule-entry 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 yesterday.
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 POST \ How it starts
The opening of the file, as written. The whole thing — 415 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create ConnectWise PSA Schedule Entry
Create a schedule entry/appointment in ConnectWise, optionally linked to a ticket.
Prerequisites
- Valid ConnectWise PSA API credentials configured
- User must have schedule creation permissions
- Member must have schedule access
Steps
-
Validate date/time inputs
- Parse start_date and end_date
- Validate end_date is after start_date
- Check for schedule conflicts (if enabled)
-
Resolve member (if provided)
GET /system/members?conditions=identifier='{member}'- Default to current authenticated user if not specified
-
Validate ticket (if ticket_id provided)
GET /service/tickets/{ticket_id}- Confirm ticket exists and is accessible
-
Resolve schedule type (if provided)
GET /schedule/types?conditions=name='{type}' -
Resolve schedule status (if provided)
GET /schedule/statuses?conditions=name='{status}' -
Create schedule entry
POST /schedule/entries Content-Type: application/json { "name": "<name>", "dateStart": "<start_date>", "dateEnd": "<end_date>", "member": {"identifier": "<member>"}, "objectId": <ticket_id>, "type": {"id": <type_id>}, "where": {"id": <location_id>}, "status": {"id": <status_id>}, "reminder": { "minutes": <reminder_minutes> } } -
Return confirmation with calendar details
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| name | string | Yes | - | Entry name/subject |
| start_date | datetime | Yes | - | Start date and time |
| end_date | datetime | Yes | - | End date and time |
| member | string | No | Current user | Member identifier |
| ticket_id | integer | No | - | Associated ticket ID |
| type | string | No | - | Schedule type |
| location | string | No | - | Location/address |
| reminder_minutes | integer | No | - | Minutes before reminder |
| status | string | No | - | Schedule status |
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.
- yesterday First seen · 415 lines · 10 tokens per session scan A ff7e60625f0c
schedule-entry is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (44 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 2,632 once invoked, about $0.0001 per session on Opus 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-09-04.
Other commands, from other repositories
research_codebase
Document codebase as-is with thoughts directory for historical context.
create_handoff
Create handoff document for transferring work to another session.
statusline-install
Add the backlog badge (📋 N open items) to the Claude Code statusLine. Wraps an existing statusLine if you have one, creates it otherwise. Edits /.claude/settings.json (or $CLAUDECONFIGDIR).
iterate_plan
Iterate on existing implementation plans with thorough research and updates.
speckit.verify-tasks
Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).
speckit.git.initialize
Initialize a Git repository with an initial commit.