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/check-agreement)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/check-agreement"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/check-agreement/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/check-agreement"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/check-agreement.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.00013 | $0.02502 |
| Opus 5 | $0.00006 | $0.01251 |
| Sonnet 5 | $0.00003 | $0.00500 |
| Haiku 4.5 | $0.00001 | $0.00250 |
Grade A, and why
check-agreement 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 5d 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 \ How it starts
The opening of the file, as written. The whole thing — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Check ConnectWise PSA Agreement
View agreement status, covered products, and remaining hours/incidents for a company.
Prerequisites
- Valid ConnectWise PSA API credentials configured
- User must have agreement read permissions
- Either company_id or agreement_id is required
Steps
-
Validate input
- Require either company_id or agreement_id
- Validate IDs are numeric
-
Retrieve agreements
If agreement_id provided:
GET /finance/agreements/{id}If company_id provided:
GET /finance/agreements?conditions=company/id={company_id}Add active filter if active_only=true:
conditions=...and cancelledFlag=false and (endDate>=2026-02-04 or endDate is null) -
Retrieve agreement additions (if include_additions=true)
GET /finance/agreements/{id}/additions -
Retrieve covered work types
GET /finance/agreements/{id}/workTypes -
Retrieve covered work roles
GET /finance/agreements/{id}/workRoles -
Format and return agreement details
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| company_id | integer | No* | - | Company ID to check |
| agreement_id | integer | No* | - | Specific agreement ID |
| include_additions | boolean | No | true | Include additions |
| active_only | boolean | No | true | Only show active |
*Either company_id or agreement_id is required
Examples
Check Company Agreements
/check-agreement --company_id 12345
Check Specific Agreement
/check-agreement --agreement_id 9876
Include All Agreements (Including Expired)
/check-agreement --company_id 12345 --active_only false
Minimal View (No Additions)
/check-agreement --agreement_id 9876 --include_additions false
Output
Company Agreements Summary
================================================================================
Agreements for Acme Corporation
================================================================================
Found 2 active agreements
--------------------------------------------------------------------------------
1. Managed Services Agreement (ID: 9876)
--------------------------------------------------------------------------------
Type: Managed Services
Status: Active
Start Date: 2025-01-01
End Date: 2025-12-31
Billing:
Cycle: Monthly
Amount: $2,500.00/month
Next Invoice: 2026-03-01
Prepaid Hours:
Purchased: 40.0 hours
Used: 24.5 hours
Remaining: 15.5 hours
Coverage:
Work Types: Remote Support, On-site Support
Work Roles: All Roles
Additions (3):
- Azure Management (+$500/month)
- 24/7 Monitoring (+$300/month)
- Additional Block Hours - 10 hrs (+$1,250, one-time)
--------------------------------------------------------------------------------
2. Break/Fix Agreement (ID: 9877)
--------------------------------------------------------------------------------
Type: Time & Materials
Status: Active
Start Date: 2024-01-01
End Date: None (Perpetual)
Billing:
Rate: $175.00/hour
Minimum: 0.25 hours
Coverage:
Work Types: All Types
Work Roles: All Roles
Note: Used for non-covered work.
================================================================================
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.
- 5d ago First seen · 408 lines · 13 tokens per session scan A e6292ddfa137
check-agreement is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 6d ago), licensed Apache-2.0. It adds 13 tokens to every session and 2,502 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
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.