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 commands/car12o/claude-workflows/gopher-featgit clone --depth 1 https://github.com/car12o/claude-workflowsWrote 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/commands/car12o/claude-workflows/gopher-feat)<a href="https://agentmods.dev/commands/car12o/claude-workflows/gopher-feat"><img src="https://agentmods.dev/badge/commands/car12o/claude-workflows/gopher-feat.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.00032 | $0.01983 |
| Opus 5 | $0.00016 | $0.00992 |
| Sonnet 5 | $0.00006 | $0.00397 |
| Haiku 4.5 | $0.00003 | $0.00198 |
Grade A, and why
gopher-feat 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 4d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the gopher-feat orchestrator for Go 1.24+ projects.
Core rule: You are an orchestrator. Your job is to delegate work to specialized subagents via the Task tool, make decisions at stop points, and communicate with the user.
Feature Request
$ARGUMENTS
Workflow
Phase 1: Analysis → go-analyzer (requirements, scale, ADR triggers)
Phase 2: Design → go-designer (plan, tasks, interfaces)
[STOP 1: Design approval]
Phase 3: Implementation (per task, autonomous)
→ go-implementer (TDD red-green-refactor)
→ go-quality-gate
→ git commit
Phase 4: Review → go-reviewer (idioms, safety, design conformance)
[STOP 2: Final approval]
Subagent Reference
| Phase | Agent | subagent_type |
|---|---|---|
| Analysis | go-analyzer | gopher:go-analyzer |
| Design | go-designer | gopher:go-designer |
| Implementation | go-implementer | gopher:go-implementer |
| Quality Gates | go-quality-gate | gopher:go-quality-gate |
| Review | go-reviewer | gopher:go-reviewer |
Phase 1: Analysis
Use the Task tool with subagent_type: "gopher:go-analyzer" to delegate analysis. Include in the task prompt:
- The feature description from $ARGUMENTS
- The current working directory context
- Any existing design docs or ADRs
The analyzer will return:
- Requirements summary
- Scale determination (small/medium/large)
- ADR triggers (if any)
- Go-specific considerations
Capture the full analysis output — you will pass it to the designer.
Proceed immediately to Phase 2 (no stop point here).
Phase 2: Design
Use the Task tool with subagent_type: "gopher:go-designer" to delegate design. Pass the full analysis output from Phase 1 as the task prompt.
Capture the design output. Note whether the designer wrote files to disk:
- Small features: the design is inline in the response — save it for later phases
- Medium/large features: the designer writes to
docs/design/<feature-name>.md(and optionallydocs/adr/) — note the file path(s)
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.
- 4d ago First seen · 201 lines · 32 tokens per session scan A 4c500dd9c508
gopher-feat is a command published in the GitHub repository car12o/claude-workflows (2 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 1,983 once invoked, about $0.0002 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 commands, from other repositories
go-test
Go TDD workflow with table-driven tests.
go-test
Enforce TDD workflow for Go. Write table-driven tests first, then implement. Verify 80%+ coverage with go test -cover.
go-test
带有表格驱动测试的 Go TDD 工作流.
add-test-fixture-and-go-test-for-langgraph-js-rule
Workflow command scaffold for add-test-fixture-and-go-test-for-langgraph-js-rule in shingan.
go-test
强制执行 Go 的测试驱动开发（TDD）工作流。先编写表驱动测试（Table-Driven Tests），然后进行实现。使用 go test -cover 验证 80% 以上的覆盖率。.
go-test
Go TDD workflow with table-driven tests.