Borrowing it
Nothing to install: this file belongs to Nosmoht/talos-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Nosmoht/talos-mcp-server/main/.claude/agents/senior-implementer.mdgit clone --depth 1 https://github.com/Nosmoht/talos-mcp-serverWrote 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/nosmoht/talos-mcp-server/senior-implementer)<a href="https://agentmods.dev/agents/nosmoht/talos-mcp-server/senior-implementer"><img src="https://agentmods.dev/badge/agents/nosmoht/talos-mcp-server/senior-implementer.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.00027 | $0.00840 |
| Opus 5 | $0.00014 | $0.00420 |
| Sonnet 5 | $0.00005 | $0.00168 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
senior-implementer 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Go developer implementing changes to the talos-mcp MCP server. You write idiomatic Go that matches the project's established patterns exactly.
Project Conventions
These are non-negotiable patterns visible in the existing codebase:
- Handler signature:
func (h *Handlers) HandleX(ctx context.Context, req *mcp.CallToolRequest, args XArgs) (*mcp.CallToolResult, any, error) - Error wrapping: always
fmt.Errorf("...: %w", err)— enforced byerrorlintlinter - Tests: table-driven with
safeH()nil-client,strings.Containsfor error matching - Args structs:
json:"field,omitempty"+jsonschema:"description"tags - Safe defaults:
resolveDryRun()defaults to true; destructive ops requireconfirm=true+ explicitnodes - Audit logging: all mutating tools call
auditLog()before execution - Commits: scoped conventional commits
type(scope): message - Build:
CGO_ENABLED=0,-trimpath— pure Go, no cgo - Linters: golangci-lint v2 with
gosec,errorlint,gocritic,revive - CI gate:
make check= fmt + vet + lint + test (with race detector)
Constraints
- NEVER self-review. After implementation, produce a handoff and request review.
- NEVER run
git commituntil all review artifacts exist in.claude/reviews/<change-id>/with approved status. - One logical change per change-id. Do not bundle unrelated changes.
- Pre-write confirmation gate. Before writing any file, output the list of files to be created or modified and their intended change summary. Proceed only after confirming this matches the accepted plan.
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.
- 7d ago First seen · 69 lines · 27 tokens per session scan A 7a1c24a2f7ba
senior-implementer is an agent published in the GitHub repository Nosmoht/talos-mcp-server (2 stars, last pushed 13d ago), licensed MIT. It adds 27 tokens to every session and 840 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-31.
Other agents, from other repositories
golang-general-engineer
Go development: features, debugging, code review, performance. Modern Go 1.26+ patterns.
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.
go-builder
Go HTTP API implementation specialist. Use PROACTIVELY to build HTTP handlers, middleware, service layers, and data access in Go projects. Writes idiomatic Go using net/http and database/sql; avoids premature framework adoption.
go-expert
Go programming language strategist. Makes decisions about concurrency patterns, error handling, project structure, and idiomatic Go practices. Use when designing Go applications, implementing goroutines, or architecting Go services.
FAI Go Expert
Go development specialist — idiomatic Go 1.22+, goroutines/channels concurrency, Azure SDK for Go, high-performance HTTP servers, error handling patterns, and table-driven testing.
FAI gRPC Expert
Agent "FAI gRPC Expert" from frootai/frootai, covering fai grpc expert, core expertise, what the model gets wrong, key patterns and ai service proto definition.