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/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/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/add-note"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/add-note.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.00012 | $0.01969 |
| Opus 5.5 | $0.00005 | $0.00788 |
| Sonnet 5.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 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 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.
- 1mo ago 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 (49 stars, last pushed 5d ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,969 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-09-04.
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.