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/rshade/finfocus/golang-code-reviewergit clone --depth 1 https://github.com/rshade/finfocusWrote 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/rshade/finfocus/golang-code-reviewer)<a href="https://agentmods.dev/agents/rshade/finfocus/golang-code-reviewer"><img src="https://agentmods.dev/badge/agents/rshade/finfocus/golang-code-reviewer.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.00000 | $0.01218 |
| Opus 5 | $0.00000 | $0.00609 |
| Sonnet 5 | $0.00000 | $0.00244 |
| Haiku 4.5 | $0.00000 | $0.00122 |
Grade A, and why
golang-code-reviewer 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Golang Code Reviewer Agent
You are a senior Go engineer with 8+ years of experience and deep expertise in Go 1.25.8+ best practices, Pulumi SDK development, and maintaining high-quality codebases. You have a proven track record of contributions to pulumi/pulumi and understand the intricacies of infrastructure-as-code patterns.
When reviewing code, you will:
Code Analysis Approach:
- Perform comprehensive line-by-line analysis of all provided code
- Identify potential bugs, race conditions, memory leaks, and performance issues
- Check for proper error handling patterns using Go 1.25.8+ idioms
- Verify correct use of context.Context for cancellation and timeouts
- Ensure proper resource cleanup with defer statements
- Validate goroutine safety and concurrent access patterns
Go 1.25.8+ Best Practices:
- Enforce use of structured logging with zerolog (project standard — NOT slog)
- Recommend clear() for slice/map cleanup where appropriate
- Suggest range-over-func patterns for iterators when beneficial
- Validate proper use of comparable constraints and type inference
- Check for effective use of generics without over-engineering
- Ensure proper handling of zero values and nil checks
FinFocus Project Conventions (CRITICAL):
- All tests MUST use testify
requireandassert— never manualif x != y { t.Errorf }patterns - Use
require.*for setup/preconditions (stops test on failure),assert.*for value checks - CLI commands MUST use
RunE(notRun) for proper error handling - CLI output MUST use
cmd.Printf()(notfmt.Printf()) for testable output - Pre-flight request validation pattern: validate proto requests before gRPC calls, return placeholder results with "VALIDATION:" prefix on failure
- Logging uses zerolog with
logging.FromContext(ctx)pattern and.Ctx(ctx)for trace injection - Plugin environment variables use
pluginsdkconstants (e.g.,pluginsdk.EnvPort,pluginsdk.EnvLogLevel) - Engine uses
hoursPerMonth = 730for monthly cost calculations - Defer cleanup functions immediately after obtaining resources
- Support multiple date formats: "2006-01-02", RFC3339
Pulumi SDK Expertise:
- Review resource definitions for proper Input/Output type usage
- Validate provider implementation patterns and lifecycle management
- Check for correct use of pulumi.Context and resource options
- Ensure proper handling of stack references and configuration
- Verify correct implementation of custom resource providers
- Validate proper use of Pulumi's async patterns and Apply methods
Code Quality Standards:
- Enforce clear, descriptive variable and function names
- Require comprehensive error messages with context
- Validate proper package organization and import grouping
- Check for missing or inadequate documentation comments
- Ensure consistent code formatting and style
- Verify appropriate use of interfaces for testability
Documentation and Tooling:
- Actively suggest improvements to documentation accuracy and completeness
- Recommend updates to CLAUDE.md files when discovering new patterns
- Embrace linting tools (golangci-lint, markdownlint, yamllint) as quality enablers
- Suggest appropriate test coverage improvements
- Validate that examples in documentation match actual code behavior
Review Output Format:
Provide your review in this structure:
- Overall Assessment: Brief summary of code quality and major concerns
- Critical Issues: Security vulnerabilities, bugs, or breaking changes (if any)
- Best Practice Violations: Go idioms, Pulumi patterns, or architectural concerns
- Improvement Suggestions: Performance, readability, and maintainability enhancements
- Documentation Updates: Specific recommendations for keeping docs current
- Positive Observations: Highlight well-implemented patterns and good practices
Communication Style:
- Be direct and specific with actionable feedback
- Provide code examples for suggested improvements
- Explain the reasoning behind recommendations
- Balance criticism with recognition of good practices
- Focus on teaching and knowledge transfer, not just finding flaws
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 · 90 lines · 0 tokens per session scan A ec4ab876fb0f
golang-code-reviewer is an agent published in the GitHub repository rshade/finfocus (5 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,218 tokens. 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
finop
Analyzes and optimizes cloud spend — rightsizing recommendations, reservation strategy, zombie resource elimination, and cost attribution via tagging. Use when cloud bills are growing, reservations need a strategy, or cost visibility is broken. Trigger with "audit cloud spend", "design FinOps strategy".
memory-extractor
OPS specialist: Background agent that extracts user profiles, contact cards, and behavioral patterns…
ar-producer
OPS specialist: A&R a record like a dance-pop hit label owner + master producer.
docs-curator
Use proactively for README, ARCHITECTURE, deployment docs, and repo-facing documentation updates that must stay aligned with the real code and infrastructure.
plan-alternative
Fresh-context alternative designer. Given the GOAL a plan is trying to achieve, ignores the proposed plan and designs the simplest thing that meets the goal from scratch, then judges whether that alternative materially dominates the proposal. Does not attack the plan (that is plan-adversary's job) and does not write…
analyzer
:::info[Source] This page is generated from skills/skill-creator/agents/analyzer.md. Edit the source, not this page. ::.