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/Lua2147/claude-toolkit-catalogWrote 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/lua2147/claude-toolkit-catalog/golang-developer)<a href="https://agentmods.dev/agents/lua2147/claude-toolkit-catalog/golang-developer"><img src="https://agentmods.dev/badge/agents/lua2147/claude-toolkit-catalog/golang-developer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/lua2147/claude-toolkit-catalog/golang-developer"><img src="https://agentmods.dev/badge/agents/lua2147/claude-toolkit-catalog/golang-developer.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.01096 |
| Opus 5.5 | $0.00008 | $0.00438 |
| Sonnet 5.5 | $0.00004 | $0.00219 |
| Haiku 4.5 | $0.00002 | $0.00110 |
Grade A, and why
golang-developer 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 1mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 1mo ago First seen · 99 lines · 19 tokens per session scan A 661e98fd0107
golang-developer is an agent published in the GitHub repository Lua2147/claude-toolkit-catalog (2 stars, last pushed 5mo ago), with no licence file. It adds 19 tokens to every session and 1,096 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other agents, from other repositories
go-tests-reviewer
Go test quality review for standard testing package patterns, table-driven tests, test helpers, httptest, benchmarks, and interface-based mocking.
hcc-frontend-go-unit-test-writer
Use this agent when you need to write unit tests for Go code. This includes pure functions, utilities, services, handlers, and business logic. Use this agent AFTER writing or modifying Go code that falls into these categories. Examples: Context: User has written a service function for data transformation. user: "I…
go-test-developer
Go testing developer. Helps design and write high-quality tests: table-driven tests, test helpers, subtests, fixtures, assertion strategies, and benchmark design.
test-engineer
MUST BE USED for writing and maintaining Go unit tests, integration tests, table-driven test patterns, test fixtures, and test utilities. Use after implementation is complete or when someone says "write tests for" or "add test coverage for" or "this needs tests.".
unit-test-writer
Write comprehensive unit tests for Go code — functions, methods, or components that need thorough test coverage.
go-test-runner
An agent that runs tests for Go backend software and returns a short summary, reporting details only for failed tests.