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/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/commands/verygoodplugins/claude-plugins/ticket-reply)<a href="https://agentmods.dev/commands/verygoodplugins/claude-plugins/ticket-reply"><img src="https://agentmods.dev/badge/commands/verygoodplugins/claude-plugins/ticket-reply/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/verygoodplugins/claude-plugins/ticket-reply"><img src="https://agentmods.dev/badge/commands/verygoodplugins/claude-plugins/ticket-reply.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.00008 | $0.00329 |
| Opus 5.5 | $0.00003 | $0.00132 |
| Sonnet 5.5 | $0.00002 | $0.00066 |
| Haiku 4.5 | $0.00001 | $0.00033 |
Grade A, and why
ticket-reply 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.
What it actually says
Create Ticket Reply
Create a draft reply for a FreeScout ticket that can be reviewed and edited before sending.
Usage
/ticket-reply <ticket>
Where <ticket> can be:
- Ticket ID (e.g.,
12345) - Ticket number (e.g.,
#1234) - FreeScout URL (e.g.,
https://support.example.com/conversation/12345)
Workflow
-
Get ticket context:
mcp__freescout__freescout_get_ticket_context({ ticket: "<ticket identifier>" }) -
Analyze the ticket (if not already done):
mcp__freescout__freescout_analyze_ticket({ ticket: "<ticket identifier>" }) -
Draft a personalized reply based on:
- Customer's specific issue
- Their history and context
- The suggested solution from analysis
- Professional, helpful tone
-
Create the draft:
mcp__freescout__freescout_create_draft_reply({ ticket: "<ticket identifier>", replyText: "<your drafted reply>" })
Guidelines
- Be empathetic and professional
- Address the specific issue raised
- Provide clear, actionable steps
- Include relevant links or resources
- End with an offer to help further
The draft will be saved in FreeScout for review before sending.
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 · 59 lines · 8 tokens per session scan A e42d6d12e058
ticket-reply is a command published in the GitHub repository verygoodplugins/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 8 tokens to every session and 329 once invoked, about $0.0000 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 commands, from other repositories
project
A command-style entry point for initializing a project with an interview, custom agents, skill workflows, and project instruction files. It also supports update, evolution, and diagnostic modes.
gws-docs
Read, create, and append content to Google Docs documents.
gws-people
Search and look up Google Contacts and directory profiles.
send-email
Send an email via Google Workspace CLI.
gws-chat
Send messages and manage Google Chat spaces.
gws-keep
List and read Google Keep notes.