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/create-quote)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/create-quote"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/create-quote/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/create-quote"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/create-quote.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.00015 | $0.00775 |
| Opus 5.5 | $0.00006 | $0.00310 |
| Sonnet 5.5 | $0.00003 | $0.00155 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
create-quote scanned grade A with 0 findings 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create ConnectWise CPQ Quote
CPQ has no create-from-scratch endpoint. A new quote is always a copy of a template or of an existing quote, then patched into shape.
Arguments
template(required) — Template GUID, template name, or the GUID of an existing quote to copyname(optional) — Name for the new quoteaccount(optional) — Customer account name to set on the copy
Prerequisites
- ConnectWise CPQ credentials configured
- At least one quote template in the tenant (
/list-templates)
Steps
-
Pick the source. If
templateis a GUID, use it astemplateId. Otherwise pass it astemplateName—cpq_create_quote_from_templateresolves the name, prompting when several templates match and erroring with the candidate list when it cannot prompt. Run/list-templatesfirst if the name is uncertain. -
Copy with
cpq_create_quote_from_template, passingtemplateIdortemplateNameplusnewNamewhen anamewas given. The copy inherits the source's tabs, line items and terms. -
Set the header with
cpq_update_quoteon the new GUID, e.g.fields={ "accountName": "$account", "expectedCloseDate": "..." }. This tool is high-impact — confirm before touchingquoteStatus,isArchive,isLostor anyorderPorter*field, which change workflow and customer-facing state. -
Adjust the lines with
cpq_search_quote_items(conditions=idQuote = "<new-guid>") andcpq_update_quote_item/cpq_create_quote_item/cpq_delete_quote_item. -
Report the new quote's
id,quoteNumber,quoteVersionand name.
Examples
From a named template
/create-quote template="Managed Services Agreement" name="Acme — Managed Services FY27" account="Acme Corp"
Revise an existing deal by copying the quote itself
/create-quote template=3f1c8d2e-1b44-4a90-9f6a-1d0f2e5b7c11 name="Acme — Renewal FY27"
Notes
- The customer records on the copy come from the source and sync from the CRM/PSA; correct
them with
cpq_update_quote_customer. There is no global customer directory to attach from. - Publishing, e-signature and porting a won quote into the PSA are not API operations — finish those in the CPQ web app.
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 · 76 lines · 15 tokens per session scan A 5c07c2ff7f03
create-quote is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (49 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 775 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other commands, from other repositories
validate-idea
Test a Shopify app idea using narrow evidence and a small experiment.
inventory-forecast
You are a senior E-commerce & Retail specialist. The user needs help with inventory forecast in the context of product catalogue optimisation, conversion rate, customer journey and retail analytics.
primer
Start with reading the CLAUDE.md file if it exists to get an understanding of the project.
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.