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/tenant-health)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/tenant-health"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/tenant-health/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/tenant-health"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/tenant-health.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.00023 | $0.00427 |
| Opus 5 | $0.00012 | $0.00214 |
| Sonnet 5 | $0.00005 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
tenant-health 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 7d 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.
What it actually says
CIPP Tenant Health Snapshot
Pulls a focused health picture for one tenant. Suitable for client check-ins, post-onboarding validation, pre-QBR prep, or "is something off with [tenant]?" investigations.
Arguments
tenant(required) — Tenant default domain, display name, or GUIDdetail(optional) — summary (default), full, or executive — controls report depth
What it checks
- Tenant freshness —
cipp_get_tenant_detailsto confirmlastRefreshis current - BPA failures —
cipp_list_bpagrouped by category, sorted by severity - Conditional Access —
cipp_list_conditional_access_policiesfiltered tostate='enabled'; flags if MFA-for-all-apps baseline is missing - MFA gaps —
cipp_list_mfa_userswith count of users without registered strong auth methods - Domain health —
cipp_list_domain_healthflagging any DMARCp=none, missing SPF, or unconfigured DKIM - Standards —
cipp_list_standardsshowing baseline standards present, mode (Report/Alert/Remediate), and last check status
Detail levels
- summary (default): Pass/fail per category, top 5 findings, one-line health verdict
- full: Every BPA result, every CA policy, all MFA gap users, all domain results
- executive: Plain-language posture summary suitable for a client-facing email
When to use this vs. the agent
Use this command for routine snapshots and quick lookups. Delegate to security-posture-reviewer when you need cross-tenant comparison, drift detection, or a structured remediation plan.
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.
- 7d ago First seen · 34 lines · 23 tokens per session scan A 5ce5c00de76e
tenant-health is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 8d ago), licensed Apache-2.0. It adds 23 tokens to every session and 427 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.