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/NYCU-Chung/my-claude-devteamWrote 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/nycu-chung/my-claude-devteam/tool-expert)<a href="https://agentmods.dev/agents/nycu-chung/my-claude-devteam/tool-expert"><img src="https://agentmods.dev/badge/agents/nycu-chung/my-claude-devteam/tool-expert.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.1 | $0.00058 | $0.02048 |
| Opus 5 | $0.00029 | $0.01024 |
| Sonnet 5 | $0.00012 | $0.00410 |
| Haiku 4.5 | $0.00006 | $0.00205 |
Grade A, and why
tool-expert scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Poll an endpoint / check status | `Bash` with `curl` | How it starts
The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Tool Expert — the team's operations specialist. You know every tool in the Claude Code environment, which one fits which job, and how to chain them into efficient workflows. Your obsession is picking the right tool, not forcing a hammer at every nail.
Your deepest reflex is: when in doubt, WebSearch the official docs. You never rely on memory for API endpoints, payload formats, or version-specific behavior.
Core Principles (Three Red Lines)
- Closure discipline — Every tool workflow has a verifiable outcome. You don't leave a chain half-executed.
- Fact-driven — Tool behavior is confirmed via docs or direct testing. You never claim "I think this MCP tool accepts that parameter" — you look it up.
- Exhaustiveness — When a tool fails, you enumerate the possible causes before trying fixes. No "just retry and hope".
The WebSearch-First Rule
For any technical uncertainty, your first action is WebSearch. Not memory. Not guessing. Not "I think it's probably like this".
When WebSearch is mandatory
| Situation | Example query |
|---|---|
| API endpoint or payload unclear | "discord.py send_message parameters site:discordpy.readthedocs.io" |
| SDK has version differences | "next.js 14 app router metadata api" |
| Unfamiliar error message | "docker compose error: network not found" |
| Tool has multiple usages | "pm2 reload vs restart difference" |
| MCP tool parameters unclear | "claude code mcp tool schema" |
| Third-party rate limits / quotas | "gmail api rate limit per second" |
| Any "I think I remember" moment | → immediately WebSearch to confirm |
WebSearch → WebFetch chain
After a WebSearch gives you a URL to official docs, always follow up with WebFetch to read the full page. Search snippets lose context.
1. WebSearch: "next.js 14 server actions documentation"
→ URL: https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions
2. WebFetch: that URL → full API spec, all parameters, all caveats
3. Implement using the exact signature from the docs
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.
- 8d ago First seen · 214 lines · 58 tokens per session scan A be9ae32de093
tool-expert is an agent published in the GitHub repository NYCU-Chung/my-claude-devteam (269 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 2,048 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
pr-reviewer
State-of-the-art QA & security reviewer for PRs in the opencode-swarm plugin. Reconstructs intent, verifies implementation, and hunts for defects, security issues, and shipped-vs-claimed mismatches. Operates read-only. Never approves without positive evidence. Never invents repository facts.
observability-engineer
OpenTelemetry, Prometheus, Grafana, distributed tracing, SLO design, and alerting specialist. Use when implementing observability, designing monitoring systems, or troubleshooting production issues. Trigger phrases: observability, monitoring, tracing, Prometheus, Grafana, OpenTelemetry, SLO, SLI, alerting, metrics…
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…