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-monitor)<a href="https://agentmods.dev/commands/wyre-ai/msp-claude-plugins/create-monitor"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/create-monitor/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-monitor"><img src="https://agentmods.dev/badge/commands/wyre-ai/msp-claude-plugins/create-monitor.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.00010 | $0.02157 |
| Opus 5 | $0.00005 | $0.01078 |
| Sonnet 5 | $0.00002 | $0.00431 |
| Haiku 4.5 | $0.00001 | $0.00216 |
Grade A, and why
create-monitor scanned grade A with 1 finding 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 12d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X GET "https://app.atera.com/api/v3/agents/{agent_id}" \ How it starts
The opening of the file, as written. The whole thing — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Atera Monitor
Create a threshold-based monitor for an agent including HTTP, TCP, or SNMP monitoring.
Prerequisites
- Valid Atera API key configured
- Agent must exist and be online
- User must have monitor creation permissions
Steps
-
Validate agent exists
curl -s -X GET "https://app.atera.com/api/v3/agents/{agent_id}" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Accept: application/json"- Verify agent exists
- Capture device and customer info
-
Validate monitor parameters
- Check monitor_type is valid (HTTP, TCP, SNMP)
- Validate target format based on type
- Set defaults for optional parameters
-
Create the monitor Based on monitor_type:
For HTTP:
curl -s -X POST "https://app.atera.com/api/v3/agents/{agent_id}/monitors/http" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "Name": "<name>", "URL": "<target>", "Interval": <interval>, "AlertSeverity": "<alert_severity>" }'For TCP:
curl -s -X POST "https://app.atera.com/api/v3/agents/{agent_id}/monitors/tcp" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "Name": "<name>", "Port": <target>, "Interval": <interval>, "AlertSeverity": "<alert_severity>" }'For SNMP:
curl -s -X POST "https://app.atera.com/api/v3/agents/{agent_id}/monitors/snmp" \ -H "X-API-KEY: $ATERA_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "Name": "<name>", "OID": "<target>", "Threshold": "<threshold>", "Interval": <interval>, "AlertSeverity": "<alert_severity>" }' -
Return monitor confirmation
- Monitor ID
- Monitor configuration summary
- Agent and customer info
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| agent_id | integer | Yes | - | The agent ID to monitor |
| monitor_type | string | Yes | - | HTTP, TCP, or SNMP |
| name | string | Yes | - | Monitor display name |
| target | string | Yes | - | URL, port, or OID to monitor |
| interval | integer | No | 5 | Check interval in minutes |
| threshold | string | No | - | Alert threshold value |
| alert_severity | string | No | Warning | Information, Warning, Critical |
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.
- 12d ago First seen · 346 lines · 10 tokens per session scan A 56bf9d252842
create-monitor is a command published in the GitHub repository WYRE-AI/msp-claude-plugins (45 stars, last pushed 9d ago), licensed Apache-2.0. It adds 10 tokens to every session and 2,157 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.