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 skills add WYRE-AI/msp-claude-plugins --skill psa-tool-mapgit 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/skills/wyre-ai/msp-claude-plugins/psa-tool-map)<a href="https://agentmods.dev/skills/wyre-ai/msp-claude-plugins/psa-tool-map"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/psa-tool-map/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/skills/wyre-ai/msp-claude-plugins/psa-tool-map"><img src="https://agentmods.dev/badge/skills/wyre-ai/msp-claude-plugins/psa-tool-map.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.00052 | $0.01078 |
| Opus 5.5 | $0.00021 | $0.00431 |
| Sonnet 5.5 | $0.00010 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
PSA Tool Map 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 3d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Curated vendors
This role is curated for: Autotask, HaloPSA, ConnectWise PSA. A connected PSA not listed here needs guided discovery: inspect the org's available tools for that connector, reason from naming and shape, and tell the human this vendor isn't fully vetted yet.
Operation map
| Abstract operation | Autotask | HaloPSA | ConnectWise PSA |
|---|---|---|---|
| List new/untriaged tickets | autotask__autotask_search_tickets |
halopsa__halopsa_tickets_list |
connectwise-psa__cw_search_tickets |
| Get ticket detail | autotask__autotask_get_ticket_details |
halopsa__halopsa_tickets_get |
connectwise-psa__cw_get_ticket |
| Update ticket (priority/status/etc.) | autotask__autotask_update_ticket |
halopsa__halopsa_tickets_update |
connectwise-psa__cw_update_ticket |
| Add a ticket note/action | autotask__autotask_create_ticket_note |
halopsa__halopsa_tickets_add_action |
connectwise-psa__cw_add_ticket_note |
| List valid ticket statuses (discover once, don't call per-run) | autotask__autotask_list_ticket_statuses |
no dedicated list tool observed — confirm via halopsa__halopsa_tickets_list field values before baking in IDs |
connectwise-psa__cw_list_statuses |
| List valid ticket priorities (discover once, don't call per-run) | autotask__autotask_list_ticket_priorities |
no dedicated list tool observed — confirm via ticket field values before baking in IDs | connectwise-psa__cw_list_priorities |
Vendor-specific gotchas
Autotask
- Priority IDs are typically not ordered by severity — discover them by name, never assume numeric ordering.
- Status/priority/queue IDs are tenant-specific — always discover once at build time, never hardcode across tenants.
- Don't call
list_*discovery tools on every routine run — it's slow enough to hit the 60-second tool timeout. Discover once, bake the IDs into the routine prompt.
HaloPSA
- No dedicated "list statuses"/"list priorities" tool was found in this
vendor's observed tool surface — confirm the actual field values by
reading a sample ticket via
halopsa_tickets_getbefore baking any ID into a routine, don't assume symmetry with Autotask's shape.
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.
- 3d ago First seen · 72 lines · 52 tokens per session scan A 446a055a431a
PSA Tool Map is a skill published in the GitHub repository WYRE-AI/msp-claude-plugins (49 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 1,078 once invoked, about $0.0002 per session on Opus 5.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-10-13.
Other skills, from other repositories
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
project
A single starting point for setting up an AI-assisted project in Claude Cowork. It asks questions about the work, reviews available add-ons, and creates project instructions, custom agents, and connected workflows.
cs-escalation
A customer-support escalation manager for complaints, VIP cases, customer feedback, and recurring service problems. It assigns escalation levels, analyses the voice of the customer, and creates weekly support summaries.
hr-operations
A skill for designing remote-work and team-operation policies. It covers flexible work, asynchronous communication, collaboration tools, productivity tracking, and employee experience.
hr-performance-review
A skill for designing and running employee performance reviews. It covers MBO, OKRs, KPIs, 360-degree feedback, review guides, and feedback conversations; OKRs set goals and measurable results, while KPIs track ongoing performance.