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/add-notegit 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/add-note)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/add-note"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/add-note.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.00012 | $0.01969 |
| Opus 5 | $0.00006 | $0.00984 |
| Sonnet 5 | $0.00002 | $0.00394 |
| Haiku 4.5 | $0.00001 | $0.00197 |
Grade A, and why
add-note 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Note to ConnectWise PSA Ticket
Add an internal or external note to a ConnectWise ticket.
Prerequisites
- Valid ConnectWise PSA API credentials configured
- User must have ticket note creation permissions
- Ticket must exist and be accessible
Steps
-
Validate ticket exists
GET /service/tickets/{id}- Confirm ticket is accessible
- Check if ticket is closed (warn if adding note to closed ticket)
-
Determine note type and destination
- If
detail_description,internal_analysis, orresolutionis true, update ticket fields - Otherwise, create a service note
- If
-
For standard notes - Create the note
POST /service/tickets/{id}/notes Content-Type: application/json { "text": "<note_text>", "detailDescriptionFlag": false, "internalAnalysisFlag": <true if flag=internal or both>, "resolutionFlag": false, "customerUpdatedFlag": <true if flag=external or both>, "processNotifications": true } -
For ticket field updates - Patch the ticket
PATCH /service/tickets/{id} Content-Type: application/json [ {"op": "replace", "path": "/detailDescription", "value": "<text>"}, {"op": "replace", "path": "/internalAnalysis", "value": "<text>"}, {"op": "replace", "path": "/resolution", "value": "<text>"} ] -
Confirm note was added
- Return note ID and timestamp
- Show note visibility
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| ticket_id | integer | Yes | - | ConnectWise ticket ID |
| text | string | Yes | - | Note content (multi-line supported) |
| detail_description | boolean | No | false | Add to detail description field |
| internal_analysis | boolean | No | false | Add to internal analysis field |
| resolution | boolean | No | false | Add to resolution field |
| flag | string | No | internal | Visibility: internal, external, both |
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 · 323 lines · 12 tokens per session scan A 544b875e7a7e
add-note 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 12 tokens to every session and 1,969 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.