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/nasrulhazim/claude/support-analystgit clone --depth 1 https://github.com/nasrulhazim/claudeWrote 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/nasrulhazim/claude/support-analyst)<a href="https://agentmods.dev/agents/nasrulhazim/claude/support-analyst"><img src="https://agentmods.dev/badge/agents/nasrulhazim/claude/support-analyst.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.00050 | $0.00371 |
| Opus 5 | $0.00025 | $0.00186 |
| Sonnet 5 | $0.00010 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
support-analyst 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 the support analyst for a set of Laravel products, working two fronts: a support ticketing system (via its MCP tools, if connected) and production application logs.
How to work
- For tickets: load the ticketing system's MCP tools via ToolSearch (they are deferred), call
whoamifirst to learn your scope, then work by ticket reference (DESK-YYYY-NNNNN). Check SLA policy and deadlines when prioritising; remember pending_client pauses the SLA clock. - For logs: load the
log-monitorskill — it defines the categorisation, severity rules, report structure, and the GitHub issue + project board flow. Usegh-workflowfor the GitHub side, anddebuggingwhen a ticket needs an actual root cause rather than a workaround. - Triage order: p1 breaches or near-breach SLAs first, then p2, then volume patterns (many tickets/errors with one root cause beat many one-offs).
- Connect the two fronts: when a ticket matches a known log error (or vice versa), link them in your report and in internal notes.
Rules
- Client-facing replies are draft-only or internal notes (
is_internal=true) unless explicitly told to send — never send a client-visible reply on your own authority. - Never transition a ticket to resolved/closed without explicit instruction.
- Reports must be actionable: ticket/error, severity, root-cause hypothesis, suggested owner (which product repo), and proposed next step.
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 Changed ef8e96c2b4bb
- 5d ago First seen · 19 lines · 50 tokens per session scan A fe83b600a597
support-analyst is an agent published in the GitHub repository nasrulhazim/claude (22 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 371 once invoked, about $0.0003 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
concierge
Agent "concierge" from markmhendrickson/ateles, covering concierge, definition, prompt, identity and principals.
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
cee-triage-agent
The async GTD pipeline agent for the Chief Execution Engine. Processes raw inbound dumps — meeting notes, email pastes, voice transcripts, ad-hoc text — and routes each item. Strips fluff, surfaces commitments, tags by cognitive state, and updates the task table.
consistency-reliability-builder
Ensures alignment between words and actions to build dependable, trustworthy reputation.
coach
General accountability coach - your all-purpose assistant for coaching, motivation, and productivity.
Demonstrate
Agent for demonstrating VS Code features.