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 verygoodplugins/claude-plugins --skill support-workflowgit clone --depth 1 https://github.com/verygoodplugins/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/verygoodplugins/claude-plugins/support-workflow)<a href="https://agentmods.dev/skills/verygoodplugins/claude-plugins/support-workflow"><img src="https://agentmods.dev/badge/skills/verygoodplugins/claude-plugins/support-workflow/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/verygoodplugins/claude-plugins/support-workflow"><img src="https://agentmods.dev/badge/skills/verygoodplugins/claude-plugins/support-workflow.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.00065 | $0.01095 |
| Opus 5.5 | $0.00026 | $0.00438 |
| Sonnet 5.5 | $0.00013 | $0.00219 |
| Haiku 4.5 | $0.00006 | $0.00110 |
Grade A, and why
support-workflow 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 1mo 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Support Workflow Skill
Manage FreeScout support tickets efficiently using the Triage-Analyze-Respond pattern.
Phase 1: TRIAGE (Discover & Prioritize)
Search for Tickets
Find tickets needing attention:
// Unassigned active tickets
mcp__freescout__freescout_search_tickets({
status: "active",
assignee: "unassigned",
pageSize: 20
})
// Recent tickets in last 24 hours
mcp__freescout__freescout_search_tickets({
status: "all",
createdSince: "24h",
includeLastMessage: true
})
// Search by keyword
mcp__freescout__freescout_search_tickets({
textSearch: "login error",
status: "active"
})
List Mailboxes
Get available mailboxes for filtering:
mcp__freescout__freescout_get_mailboxes({})
Phase 2: ANALYZE (Understand the Issue)
Get Full Ticket Details
mcp__freescout__freescout_get_ticket({
ticket: "<ticket-id-or-url>",
includeThreads: true
})
Analyze Issue Type & Solution
mcp__freescout__freescout_analyze_ticket({
ticket: "<ticket-id-or-url>"
})
The analysis returns:
- Issue Type: Bug, feature request, how-to, billing, etc.
- Root Cause: What's causing the problem
- Suggested Solution: Recommended resolution steps
- Priority: Based on impact and urgency
Get Customer Context
mcp__freescout__freescout_get_ticket_context({
ticket: "<ticket-id-or-url>"
})
Returns customer history, previous tickets, and relevant context for personalization.
Phase 3: RESPOND (Take Action)
Create Draft Reply
Draft a response that can be reviewed before sending:
mcp__freescout__freescout_create_draft_reply({
ticket: "<ticket-id-or-url>",
replyText: "Hi [Customer Name],\n\nThank you for reaching out..."
})
Add Internal Note
Add notes for team collaboration (not visible to customer):
mcp__freescout__freescout_add_note({
ticket: "<ticket-id-or-url>",
note: "Escalated to dev team - suspected bug in v2.3.1"
})
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.
- 1mo ago First seen · 197 lines · 65 tokens per session scan A 01ca9fdd6da7
support-workflow is a skill published in the GitHub repository verygoodplugins/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 65 tokens to every session and 1,095 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
career-portfolio
A portfolio-building skill for Korean job seekers that organizes projects and explains their work for development, design, marketing, and planning roles.
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.
collab-conflict
A guide for handling difficult workplace colleagues and recurring communication conflicts.
collab-feedback-loop
A guide for giving and receiving workplace feedback about specific actions and their effects.
collab-meeting
A meeting facilitation aid that helps define the purpose, plan the agenda, guide discussion, record decisions, and assign follow-up actions.
collab-negotiation
A guide for preparing one-to-one workplace conversations, persuasion, requests, and negotiations.