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 skills/notque/vexjoy-agent/go-patternsnpx skills add notque/vexjoy-agent --skill go-patternsgit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/skills/notque/vexjoy-agent/go-patterns)<a href="https://agentmods.dev/skills/notque/vexjoy-agent/go-patterns"><img src="https://agentmods.dev/badge/skills/notque/vexjoy-agent/go-patterns.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.00019 | $0.01924 |
| Opus 5 | $0.00010 | $0.00962 |
| Sonnet 5 | $0.00004 | $0.00385 |
| Haiku 4.5 | $0.00002 | $0.00192 |
Grade A, and why
go-patterns 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 today.
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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Patterns Skill
Umbrella skill for Go development: Google style, testing, concurrency, error handling, failure modes, code review, SAP CC conventions, and quality gates. Load the references relevant to the task.
Google Style Precedence
Use this precedence when guidance differs:
- The target repository's explicit rules and required compatibility constraints.
- The Google Go Style Guide's canonical rules.
- Google Go Style Decisions' normative guidance.
- Google Go Style Best Practices' non-canonical recommendations.
- Task-specific references below.
Prefer local consistency only where the Google guide allows judgment. Do not create unrelated churn merely to restyle existing code. For new and nearby changed code, follow the current pinned guidance. Record a conscious exception when repository rules, generated-code constraints, or compatibility requirements require one.
Reference Loading Table
| Signal | Load These Files | Why |
|---|---|---|
| Google-specific style decisions | Relevant sections under google-style-guide/ |
Check the pinned conventions needed for the task |
| Testing | testing.md |
Writing, fixing, or reviewing Go tests |
| Concurrency | concurrency.md |
Goroutines, channels, sync primitives, race conditions |
| Error handling | error-handling.md |
Error wrapping, sentinels, custom types, errors.Is/As |
| Review patterns | preferred-patterns.md |
Detecting code smells, over-engineering, bad Go patterns |
| Code review | code-review.md |
Reviewing Go code or PRs for quality |
| SAP CC conventions | sapcc-conventions.md |
Working in sapcc/* repos with go-bits |
| Quality gate | quality-gate.md |
Running make check, linting, pre-commit validation |
Instructions
Step 1: Identify the Go Domain
Classify the task into one or more domains, then load the corresponding reference files. Only load what is needed -- do not load all references for every task.
| Domain | Load Reference | When |
|---|---|---|
| Testing | references/testing.md |
Writing, fixing, or reviewing Go tests |
| Concurrency | references/concurrency.md |
Goroutines, channels, sync primitives, race conditions |
| Error handling | references/error-handling.md |
Error wrapping, sentinels, custom types, errors.Is/As |
| Review patterns | references/preferred-patterns.md |
Detecting code smells, over-engineering, bad Go patterns |
| Code review | references/code-review.md |
Reviewing Go code or PRs for quality |
| SAP CC conventions | references/sapcc-conventions.md |
Working in sapcc/* repos with go-bits |
| Quality gate | references/quality-gate.md |
Running make check, linting, pre-commit validation |
What ships with it
60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/code-review.md 12 KB
- references/code-review/common-review-comments.md 6.6 KB
- references/concurrency.md 11 KB
- references/concurrency/concurrency-patterns.md 5.3 KB
- references/error-handling.md 11 KB
- references/error-handling/patterns.md 4.2 KB
- references/google-style-guide/ATTRIBUTION.md 802 B
- references/google-style-guide/best-practices/part-01.md 10.0 KB
- references/google-style-guide/best-practices/part-02.md 15 KB
- references/google-style-guide/best-practices/part-03.md 14 KB
- references/google-style-guide/best-practices/part-04.md 14 KB
- references/google-style-guide/best-practices/part-05.md 11 KB
- references/google-style-guide/best-practices/part-06.md 14 KB
- references/google-style-guide/best-practices/part-07.md 16 KB
- references/google-style-guide/best-practices/part-08.md 11 KB
- references/google-style-guide/best-practices/part-09.md 14 KB
- references/google-style-guide/best-practices/part-10.md 17 KB
- references/google-style-guide/decisions/part-01.md 15 KB
- references/google-style-guide/decisions/part-02.md 13 KB
- references/google-style-guide/decisions/part-03.md 11 KB
- references/google-style-guide/decisions/part-04.md 8.4 KB
- references/google-style-guide/decisions/part-05.md 9.8 KB
- references/google-style-guide/decisions/part-06.md 15 KB
- references/google-style-guide/decisions/part-07.md 13 KB
- references/google-style-guide/decisions/part-08.md 14 KB
- references/google-style-guide/decisions/part-09.md 15 KB
- references/google-style-guide/decisions/part-10.md 8.3 KB
- references/google-style-guide/guide/part-01.md 16 KB
- references/google-style-guide/guide/part-02.md 3.0 KB
- references/google-style-guide/index.md 8.4 KB
- references/google-style-guide/LOAD_ORDER.md 1.1 KB
- references/google-style-guide/SHA256SUMS 313 B
- references/google-style-guide/UPSTREAM_REVISION 41 B
- references/preferred-patterns.md 13 KB
- references/preferred-patterns/code-examples.md 12 KB
- references/quality-gate.md 7.4 KB
- references/quality-gate/common-lint-errors.json 7.6 KB
- references/quality-gate/examples.md 11 KB
- references/quality-gate/expert-review-patterns.md 4.5 KB
- references/quality-gate/makefile-targets.json 5.1 KB
- references/sapcc-conventions.md 35 KB
- references/sapcc-conventions/api-design-detailed.md 23 KB
- references/sapcc-conventions/architecture-patterns.md 19 KB
- references/sapcc-conventions/build-ci-detailed.md 19 KB
- references/sapcc-conventions/error-handling-detailed.md 20 KB
- references/sapcc-conventions/extended-patterns.md 7.1 KB
- references/sapcc-conventions/go-bits-philosophy-detailed.md 24 KB
- references/sapcc-conventions/library-reference.md 14 KB
- references/sapcc-conventions/pr-mining-insights.md 18 KB
- references/sapcc-conventions/review-standards.md 11 KB
- references/sapcc-conventions/sapcc-code-patterns.md 46 KB
- references/testing.md 9.7 KB
- references/testing/go-benchmark-and-concurrency.md 5.3 KB
- references/testing/go-test-patterns.md 9.0 KB
- scripts/bench-compare.sh 7.1 KB runs code
- scripts/check-errors.sh 7.1 KB runs code
- scripts/check-interface-compliance.sh 6.4 KB runs code
- scripts/check-sapcc-auth-ordering.sh 5.5 KB runs code
- scripts/check-sapcc-httptest.sh 4.4 KB runs code
- scripts/check-sapcc-identify-endpoint.sh 5.8 KB runs code
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.
- today Changed · -15 lines 2a8034839463
- yesterday First seen · 198 lines · 19 tokens per session scan A e87429f9a675
go-patterns is a skill published in the GitHub repository notque/vexjoy-agent (420 stars, last pushed today), licensed MIT. It adds 19 tokens to every session and 1,924 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-09-03.
Other skills, from other repositories
golang-rules
Go coding rules: style, patterns, security, testing. Triggers: .go, go.mod, go.sum, Gin, Echo, Gorilla, testing, gofmt.
go-code-reviewer
Review Go code with a defect-first approach using repository policy (constitution.md first, then AGENTS.md fallback). Use for code review, PR review, quality checks, risk analysis, and regression detection.
go-dependency-audit
Go dependency audit specialist for CVE scanning (govulncheck), license risk triage, outdated dependency detection, upgrade impact analysis, and supply chain security. ALWAYS use when auditing go.mod dependencies, running govulncheck, checking license compatibility, planning dependency upgrades, or investigating supply…
unit-test
Use when the user asks for unit tests (e.g, "单元测试", "unit test"), wants to add/fix Go tests, wants table-driven and subtest organization, or wants to enforce a minimum coverage gate (default 80% for logic packages). Prioritize bug discovery (especially boundary, mapping loss, and concurrency defects) over test volume.…
fuzzing-test
Generate Go fuzz tests (Go 1.18+ testing.F) for specified code when users ask for fuzzing/模糊测试/fuzz test generation, parser robustness, round-trip, or differential fuzzing. Always run an applicability gate first; if the target is not suitable, explain concrete reasons and stop without writing fuzz test code.
go-benchmark
Go performance benchmarking and pprof profiling specialist. ALWAYS use when writing benchmark functions (testing.B), generating or reading pprof profiles, interpreting flame graphs, finding memory allocation hotspots, comparing implementations with benchstat, or measuring ns/op / B/op / allocs/op. In Go code contexts…