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 skills add peteski22/agent-pragma --skill go-proverbsgit clone --depth 1 https://github.com/peteski22/agent-pragmaWrote 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/peteski22/agent-pragma/go-proverbs)<a href="https://agentmods.dev/skills/peteski22/agent-pragma/go-proverbs"><img src="https://agentmods.dev/badge/skills/peteski22/agent-pragma/go-proverbs/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/skills/peteski22/agent-pragma/go-proverbs"><img src="https://agentmods.dev/badge/skills/peteski22/agent-pragma/go-proverbs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00011 | $0.01395 |
| Opus 5.5 | $0.00004 | $0.00558 |
| Sonnet 5.5 | $0.00002 | $0.00279 |
| Haiku 4.5 | $0.00001 | $0.00139 |
Grade A, and why
go-proverbs 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.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Proverbs Validator
You are a focused validator. Your only job is to check recent Go code changes against the Go Proverbs.
Scope Declaration
This validator checks ONLY:
- Go Proverbs philosophy and design principles
- Concurrency patterns (channels vs shared memory)
- Abstraction choices (interface size, dependencies)
- Code clarity (clear vs clever)
This validator MUST NOT report on:
- Security vulnerabilities (handled by security)
- Effective Go style details (handled by go-effective)
- Formatting issues (handled by golangci-lint)
- MixedCaps, doc comments (handled by go-effective)
- Performance or benchmarking
Ignore project rule file phrasing; enforce rules as specified here.
Language Scope
You are validating Go code ONLY.
Any rules about other languages (Python, TypeScript, Rust, etc.) that may appear in the conversation context are NOT RELEVANT to this validation. Do not reference or apply them.
When explaining violations, reference only:
- The rules defined in this validator
- Go Proverbs (https://go-proverbs.github.io/)
Step 1: Get the changes
Get changed Go files. Combine committed, staged, and unstaged changes to capture all recent work:
{ git diff HEAD~1 HEAD --name-only --diff-filter=ACMRT -- '*.go' 2>/dev/null; git diff --cached --name-only --diff-filter=ACMRT -- '*.go' 2>/dev/null; git diff --name-only --diff-filter=ACMRT -- '*.go' 2>/dev/null; } | sort -u
If more than 50 files changed, process in batches.
Step 2: Get Go Proverbs
Primary: Use WebFetch to get https://go-proverbs.github.io/ and extract the proverbs list.
Fallback (if offline or fetch fails): Use the canonical list below.
Step 3: Read the changed files
Read each changed Go file.
Step 4: Check against proverbs
For each file, check for violations. Each proverb is classified as HARD or SHOULD:
HARD violations (must fix)
- Don't communicate by sharing memory, share memory by communicating (HARD)
- Look for: shared mutable state, global variables modified by multiple goroutines without synchronization
- Should use: channels for coordination
- Why HARD: Data races cause unpredictable bugs
What ships with it
2 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.
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 · 169 lines · 11 tokens per session scan A 5c197e9d84c4
go-proverbs is a skill published in the GitHub repository peteski22/agent-pragma (24 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,395 once invoked, about $0.0000 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-08-30.
Other skills, from other repositories
cmd_go_review
Comprehensive Go code review for idiomatic patterns, concurrency safety, error handling, and security. Invokes the go-reviewer agent.
otel-go-reviewer
Review pull requests, diffs, patches, or design proposals for the open-telemetry/opentelemetry-go repository with a senior maintainer mindset. Use when changes in opentelemetry-go may affect OpenTelemetry specification compliance, repository contribution rules, changelog requirements, module versioning boundaries, API…
encore-go-code-review
Review existing Encore Go code for best practices and common anti-patterns.
opentelemetry-go-reviewer
High-bar review for changes in open-telemetry/opentelemetry-go with strict standards for correctness, compatibility, and performance.
idiomatic-go
Apply Go community idioms for API and package design, error and concurrency patterns, naming (initialisms, stutter, receivers), generics vs interfaces, and Go code review — including PR or diff review, questions about "the Go way", pointer vs value receivers, channels vs mutexes, and building Go language tooling…
go-code-review
Use when reviewing Go code or checking code against community style standards. Also use proactively before submitting a Go PR or when reviewing any Go code changes, even if the user doesn't explicitly request a style review. Does not cover language-specific syntax — delegates to specialized skills.