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.
npx agentmods add commands/wyre-ai/msp-claude-plugins/security-posturegit 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/security-posture)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/security-posture"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/security-posture.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 | $0.00015 | $0.00403 |
| Opus 5 | $0.00008 | $0.00201 |
| Sonnet 5 | $0.00003 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
security-posture 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 today.
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
Security Posture
Prerequisites
- Valid Blumira JWT token configured
- Active findings and agent data in the organization
Steps
- Call
blumira_findings_listwithstatus.eq=10to get all open findings - Call
blumira_findings_listwithstatus.eq=30andcreated.gt=<days ago>for recent resolutions - Call
blumira_agents_devices_listto get device/agent inventory - Compile a posture report:
- Open Findings Summary: Total count, breakdown by severity (CRITICAL/HIGH/MEDIUM/LOW)
- Resolution Activity: Findings resolved in the lookback period, by resolution type
- Agent Coverage: Total devices, active vs inactive, stale agents
- Risk Assessment: Highlight critical gaps (unresolved CRITICAL findings, offline agents)
- Provide actionable recommendations based on the data
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| days | number | No | Lookback period for trend analysis (default 30) |
Examples
Basic Usage
/security-posture
7-Day Review
/security-posture --days 7
Error Handling
- No findings data: Report clean finding posture, focus on agent coverage
- No agent data: Report finding posture only, note agent data unavailable
- Large dataset: Use date filters to limit scope
Related Commands
/finding-triage- Triage the open findings identified in the posture review/agent-inventory- Detailed device/agent inventory/msp-overview- MSP-wide posture across all accounts
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.
- today First seen · 57 lines · 15 tokens per session scan A afd1d0956c2e
security-posture is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (44 stars, last pushed yesterday), licensed Apache-2.0. It adds 15 tokens to every session and 403 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
research_codebase
Document codebase as-is with thoughts directory for historical context.
iterate_plan
Iterate on existing implementation plans with thorough research and updates.
speckit.verify-tasks
Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).
vibe-check
Audit a vibe-coded app across the six things that actually block shipping, and get a prioritized fix list.
evaluate
Execute Evaluate stage to validate generated framework artifacts.
git
Git operations with intelligent commit messages and workflow optimization.