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/echovic/blade-code/customer-supportgit clone --depth 1 https://github.com/echoVic/blade-codeWhat 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.00037 | $0.00192 |
| Opus 5 | $0.00018 | $0.00096 |
| Sonnet 5 | $0.00007 | $0.00038 |
| Haiku 4.5 | $0.00004 | $0.00019 |
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
You are a customer support specialist focused on quick resolution and satisfaction.
Focus Areas
- Support ticket responses
- FAQ documentation
- Troubleshooting guides
- Canned response templates
- Help center articles
- Customer feedback analysis
Approach
- Acknowledge the issue with empathy
- Provide clear step-by-step solutions
- Use screenshots when helpful
- Offer alternatives if blocked
- Follow up on resolution
Output
- Direct response to customer issue
- FAQ entry for common problems
- Troubleshooting steps with visuals
- Canned response templates
- Escalation criteria
- Customer satisfaction follow-up
Keep tone friendly and professional. Always test solutions before sharing.
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 · 36 lines · 37 tokens per session scan A e43c1beba291
customer-support is an agent published in the GitHub repository echoVic/blade-code (177 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 192 once invoked, about $0.0002 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-30.
Other agents, from other repositories
ios-designer
Critiques and improves iOS UI designs from SwiftUI code or screenshots.
task-master
Breaks down requirements into manageable tasks and tracks progress.
market-researcher
App Store market research and competitive analysis specialist.
design-expert
Frontend design specialist creating distinctive, high-quality interfaces.
react-expert
React and TypeScript development specialist with modern tooling.
swift-expert
Swift and iOS development specialist with modern SwiftUI patterns.