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 agentmods add commands/verygoodplugins/claude-plugins/ticket-analyzegit clone --depth 1 https://github.com/verygoodplugins/claude-pluginsWhat 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 | $0.00014 | $0.00248 |
| Opus 5 | $0.00007 | $0.00124 |
| Sonnet 5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
Grade A, and why
ticket-analyze 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 2d 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
Analyze Ticket
Analyze a FreeScout ticket to determine the issue type, root cause, and suggested solution.
Usage
/ticket-analyze <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)
Action
Use the mcp__freescout__freescout_analyze_ticket tool:
mcp__freescout__freescout_analyze_ticket({
ticket: "<ticket identifier>"
})
Output
Present the analysis including:
- Issue Type: Bug, feature request, how-to question, billing, etc.
- Root Cause: What's causing the issue
- Suggested Solution: Recommended steps to resolve
- Priority Level: Based on impact and urgency
- Related Context: Any relevant product areas or past similar tickets
Use this analysis to inform your response to the customer or to guide the support team.
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.
- 2d ago First seen · 40 lines · 14 tokens per session scan A e4c9405adefb
ticket-analyze is a command published in the GitHub repository verygoodplugins/claude-plugins (2 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 248 once invoked, about $0.0001 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-31.
Other commands, from other repositories
triage
AI-powered reachability triage for dependency vulnerabilities. Scans for CVEs then searches your source code to estimate whether each vulnerable API is actually called. Outputs a prioritized FOUNDINSOURCE / UNCERTAIN / NOTFOUNDINGREP report.
prioritize
Explicitly invoke prioritization with optional context or file path. Usage: /prioritize or /prioritize [path to file with tasks].
excalidraw
Generate or modify Excalidraw diagrams from descriptions or code analysis.
flow
Show fakoli-flow's 6 skills, the workflow pipeline, and the currently detected project state (language, crew availability). Takes no arguments — use /fakoli-flow: to trigger a skill.
promote
Move .memory/ artifacts to permanent knowledge locations.
checkpoint
Create or update .memory/ with current conversation state.