Borrowing it
Nothing to install: this file belongs to WYRE-AI/msp-claude-plugins. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/WYRE-AI/msp-claude-plugins/main/AGENTS.mdgit 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/instructions/wyre-ai/msp-claude-plugins/agents-md)<a href="https://agentmods.dev/instructions/wyre-ai/msp-claude-plugins/agents-md"><img src="https://agentmods.dev/badge/instructions/wyre-ai/msp-claude-plugins/agents-md.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.01066 | $0.01066 |
| Opus 5 | $0.00533 | $0.00533 |
| Sonnet 5 | $0.00213 | $0.00213 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
msp-claude-plugins AGENTS.md 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Guidance for AI Agents
This file provides guidance for AI coding agents (Claude Code, Codex, Gemini CLI, etc.) working in this repository.
What This Repo Is
A collection of Claude Code plugins for MSP vendors — skills, commands, and MCP integrations for tools like Autotask, ConnectWise, NinjaOne, HaloPSA, SentinelOne, Huntress, and others. The intended users are MSP technicians running Claude Code day-to-day.
Directory Structure
msp-claude-plugins/
├── <vendor>/
│ └── <product>/
│ ├── .claude-plugin/
│ │ └── plugin.json # Plugin manifest
│ ├── skills/
│ │ └── <skill-name>/
│ │ ├── SKILL.md # The skill itself (loaded by Claude Code)
│ │ └── REFERENCE.md # Optional: full param/field reference
│ ├── agents/
│ │ └── <agent-name>.md # Persona-driven workflow agents
│ └── commands/
│ └── <command>.md # Slash command definitions
├── _standards/ # Quality standards — read before writing skills
├── _templates/ # Templates for skills, agents, commands, plugins
├── shared/ # Vendor-agnostic skills
└── CONTRIBUTING.md # Contribution guidelines
Writing Skills
Skills are Markdown files with YAML frontmatter. They are injected into Claude's context when triggered.
SKILL.md structure:
---
name: kebab-case-skill-name
description: "Use when [specific trigger]. Covers [scope]."
metadata:
version: "1.0.0"
openclaw:
requires:
bins:
- npx
---
# Skill Title
## Workflow
1. **Step** — what to do, what to check, what to do on failure
## Tools
### `tool_name`
Brief description. Required params. Common optional params.
**Example:** concrete JSON example
## Field Reference / Error Reference
Point to REFERENCE.md if the tables are long.
Key rules:
namemust be kebab-casedescriptionmust start with "Use when..."- Keep SKILL.md under ~150 lines; move verbose tables to REFERENCE.md
- Include concrete JSON examples, not just param lists
- Include error recovery steps in the workflow
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 · 118 lines · 1,066 tokens per session scan A 07536b75f2fe
msp-claude-plugins AGENTS.md is an instructions file published in the GitHub repository WYRE-AI/msp-claude-plugins (44 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,066 tokens to every session, about $0.0053 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-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.