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/agent-inventorygit 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/agent-inventory)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/agent-inventory"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/agent-inventory.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.00013 | $0.00331 |
| Opus 5 | $0.00006 | $0.00166 |
| Sonnet 5 | $0.00003 | $0.00066 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
agent-inventory 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 2d 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
Agent Inventory
Prerequisites
- Valid Blumira JWT token configured
- Agent deployment in the organization
Steps
- Call
blumira_agents_devices_listwithpage_size=100andorder_by=-last_seen - If OS filter provided, add
os.contains=<value> - Page through all results to build complete inventory
- Present a summary:
- Total device count
- Breakdown by OS
- Breakdown by status (active, inactive, etc.)
- Devices with stale
last_seentimestamps (>24h)
- Call
blumira_agents_keys_listto show available deployment keys - Highlight any coverage gaps or health concerns
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| os | string | No | Filter by OS (Windows, Linux, macOS) |
| status | string | No | Filter by agent status |
Examples
Basic Usage
/agent-inventory
Windows Devices Only
/agent-inventory --os Windows
Error Handling
- No devices found: Verify agents are deployed and token has access
- Pagination timeout: Use OS filter to narrow results
Related Commands
/security-posture- Overall security posture including agent coverage/msp-overview- MSP-wide device inventory
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.
- 2d ago First seen · 57 lines · 13 tokens per session scan A 8f131b4036c9
agent-inventory is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (44 stars, last pushed 3d ago), licensed Apache-2.0. It adds 13 tokens to every session and 331 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
speckit.verify-tasks
Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).
speckit.git.initialize
Initialize a Git repository with an initial commit.
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.