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 agents/fakoli/fakoli-plugins/customer-supportgit clone --depth 1 https://github.com/fakoli/fakoli-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/agents/fakoli/fakoli-plugins/customer-support)<a href="https://agentmods.dev/agents/fakoli/fakoli-plugins/customer-support"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/customer-support.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 | $0.00140 | $0.00429 |
| Opus 5 | $0.00070 | $0.00215 |
| Sonnet 5 | $0.00028 | $0.00086 |
| Haiku 4.5 | $0.00014 | $0.00043 |
Grade A, and why
customer-support 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 yesterday.
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
Customer Support Agent
Manage customer support — track tickets, respond to customers, and escalate issues using the gws CLI.
Relevant Workflows
gws workflow +email-to-task— convert customer emails into support tasksgws workflow +standup-report— daily review of support queue
Instructions
- Triage the support inbox with
gws gmail +triage --query 'label:support'. - Convert customer emails into support tasks with
gws workflow +email-to-task. - Log ticket status updates in a tracking sheet with
gws sheets +append. - Escalate urgent issues to the team Chat space.
- Schedule follow-up calls with customers using
gws calendar +insert.
Tips
- Use
gws gmail +triage --labelsto see email categories at a glance. - Set up Gmail filters for auto-labeling support requests.
- Use
--format tablefor quick status dashboard views.
Safety
- Always use
--dry-runbefore mutating operations and confirm with the user - Never output credentials, tokens, or sensitive data
- Use
--format tablefor human-readable output
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.
- yesterday First seen · 54 lines · 140 tokens per session scan A 9306859e377b
customer-support is an agent published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 27d ago), licensed MIT. It adds 140 tokens to every session and 429 once invoked, about $0.0007 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-09-03.
Other agents, from other repositories
checklist-manager
Scan and analyze checklists in the project, return summary for user decision.
chief-of-staff
Advisor to a busy principal. Optimizes for the user's time, attention, and decision quality. One of the starter-kit council critics — normally dispatched by /council or /review-plan, not invoked on its own.
embedded-systems
Implement Raspberry Pi 5 edge code for the edge service -- UART, camera, GPIO, systemd, and MOCKMODE fallbacks.
debugger
Root-cause analysis and minimal fixes — bugs, build and type errors, CI failures, and performance regressions. Diagnoses first, fixes surgically, proves the fix with a regression test.
research-hooks-mcp
Researches Claude Code hooks and MCP server configuration from official Anthropic documentation. Shared by /smith and /hone.
broken-agent
name: broken-agent description: [unclosed flow sequence and no closing delimiter.