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/questionnaire)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/questionnaire"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/questionnaire.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.00014 | $0.00938 |
| Opus 5 | $0.00007 | $0.00469 |
| Sonnet 5 | $0.00003 | $0.00188 |
| Haiku 4.5 | $0.00001 | $0.00094 |
Grade A, and why
questionnaire 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 4d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Questionnaire
Walk the standard cyber-insurance renewal question set (MFA, EDR, backups, incident response, security awareness training) for a client and draft evidence-backed answers, flagging anything that can't be answered with current tool coverage.
Prerequisites
- Conduit MCP Gateway connected (
conduit) - CIPP connected at minimum (covers the MFA question, the strongest-weighted question in most questionnaires); Liongard, IT Glue/Hudu, and any EDR/PSA connectors strengthen coverage of the remaining questions
Steps
- Discover available tools. Call
conduit__search_toolsto determine which connectors are available for this client — MFA/CIPP, EDR/MDR (Huntress, SentinelOne, RocketCyber), documentation (IT Glue/Hudu), and PSA (HaloPSA, Autotask) if present. - Resolve the client against the connected tenant/documentation records.
- Invoke the
questionnaire-autofilleragent for the resolved client. The agent walks the standard question set from theinsurance-questionnairesskill, pulling live evidence per question and labeling each answer evidence-backed, documented-only, or unable to verify. - Present the draft answers followed by a clearly separated "cannot answer with current tool coverage" list, each with a recommended next step.
Arguments
| Argument | Required | Default | Description |
|---|---|---|---|
client |
Yes | — | The client/organization name to draft the questionnaire for |
Examples
Draft the standard questionnaire for a renewal
/compliance-pack:questionnaire "Acme Corp"
Output
================================================================================
Cyber Insurance Questionnaire Draft — Acme Corp
================================================================================
Draft Date: 2026-07-14
Connectors used: CIPP, IT Glue
Connectors unavailable: Huntress, SentinelOne, RocketCyber (no EDR/MDR connected)
--------------------------------------------------------------------------------
Drafted Answers
--------------------------------------------------------------------------------
Q: Is MFA enforced for all users, including privileged/admin accounts?
A: MFA is enforced for 39 of 41 users (95%) via conditional access policy
"Require MFA - All Users." 2 exceptions: 1 break-glass account (by design),
1 legacy service account pending remediation.
Evidence: Evidence-backed
Citation: cipp__list_mfa_users, cipp__list_conditional_access_policies
Q: Is EDR deployed across all endpoints?
A: Unable to verify — no EDR/MDR connector is currently connected for this client.
Evidence: Unable to Verify
Citation: conduit__search_tools (no match)
Q: Are backups tested via periodic restore tests?
A: A backup/DR runbook is documented, last updated 2025-11-03. No live
test-restore evidence source is connected; testing cadence cannot be
confirmed from tooling.
Evidence: Documented-only
Citation: itglue__search_documents ("Backup & DR Runbook")
--------------------------------------------------------------------------------
Cannot Answer With Current Tool Coverage
--------------------------------------------------------------------------------
1. EDR/endpoint coverage — connect Huntress, SentinelOne, or RocketCyber to close this gap.
2. Backup restore-testing cadence — connect a backup platform, or confirm manually before submission.
3. Security awareness training — no training platform connector available; confirm current
program status directly before answering.
--------------------------------------------------------------------------------
Notes for the MSP
--------------------------------------------------------------------------------
Underwriter is likely to follow up on the 2 MFA exceptions and the unverified
backup-testing cadence — have specifics ready before submitting.
================================================================================
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.
- 4d ago First seen · 109 lines · 14 tokens per session scan A bb4937a9cf0c
questionnaire is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 5d ago), licensed Apache-2.0. It adds 14 tokens to every session and 938 once invoked, about $0.0001 per session on Opus 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.