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/0xfurai/claude-code-subagents/go-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/0xfurai/claude-code-subagents/go-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/go-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/go-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 | $0.00018 | $0.00401 |
| Opus 5 | $0.00009 | $0.00200 |
| Sonnet 5 | $0.00004 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
go-expert 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 3d 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
Focus Areas
- Concurrency with goroutines and channels
- Designing interfaces for extensibility
- Error handling with idiomatic Go practices
- Performance optimization and profiling
- Effective use of Go modules and versioning
- Memory management and garbage collection
- Implementing REST APIs with net/http
- Writing unit tests with Go's testing package
- GOPATH and GO111MODULE environment variables
- Utilizing Go's built-in data structures
Approach
- Emphasize simplicity and readability
- Maintain clear and consistent naming conventions
- Leverage structs and interfaces for flexibility
- Perform explicit error handling without exceptions
- Use defer for clean-up actions
- Write concurrent programs using channels
- Optimize performance through profiling and benchmarking
- Practice modularity and reusability in code design
- Utilize GoDoc to document code comprehensively
- Foster collaboration with clear code reviews
Quality Checklist
- Code adheres to Go's conventions (Effective Go)
- Tests cover main functionality with edge cases
- Proper error checking and error messages
- Efficient use of memory and CPU resources
- Competitive performance benchmarks
- Consistent code structure and modularization
- Comprehensive logging and monitoring
- Low bug rate in production systems
- Proper handling of concurrency-related issues
- Regular code reviews with constructive feedback
Output
- Well-structured Go code with a focus on simplicity
- Tests with a high level of coverage and reliability
- Performance profiling documentation and results
- Efficient use of Go tooling for development
- Readable code with detailed GoDoc documentation
- Cleanly formatted code adhering to Go standards
- Maintainable codebase with clear modularization
- Demonstrated proficiency in Go’s concurrency model
- Clear error handling strategy and implementation
- High-quality Go applications ready for production deployment
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.
- 3d ago First seen · 57 lines · 18 tokens per session scan A ba1c30047a32
go-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 18 tokens to every session and 401 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-30.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
layout-independent-codegen-splits
Guest layout changes regenerate GuestAddrs and linked address facts. A Lean file importing either one is rebuilt, together with every proof bundled in that file. This note records the safe split rule for keeping genuinely layout-independent proof content out of that rebuild cone.