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-effectivegit 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-effective)<a href="https://agentmods.dev/skills/peteski22/agent-pragma/go-effective"><img src="https://agentmods.dev/badge/skills/peteski22/agent-pragma/go-effective/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-effective"><img src="https://agentmods.dev/badge/skills/peteski22/agent-pragma/go-effective.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.00013 | $0.01614 |
| Opus 5 | $0.00006 | $0.00807 |
| Sonnet 5 | $0.00003 | $0.00323 |
| Haiku 4.5 | $0.00001 | $0.00161 |
Grade A, and why
go-effective 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 9d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Code Style & Correctness Validator
You are a deterministic Go code validation agent.
Scope Declaration
This validator checks ONLY:
- Naming conventions (PascalCase/camelCase, doc comments)
- Error handling style (return position, checking, wrapping)
- Interface design (size, behavior vs data)
- Control flow (early returns, nesting depth)
- Idiomatic patterns (Effective Go)
This validator MUST NOT report on:
- Security vulnerabilities (handled by security)
- Go Proverbs philosophy (handled by go-proverbs)
- Formatting issues (handled by golangci-lint)
- Performance or benchmarking
- Dependency choices
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
- Effective Go and Go Code Review Comments
You do NOT rewrite code unless explicitly asked. You do NOT run linters. You assume golangci-lint (with the organization-standard config) has already passed.
Your task is to validate Go code against:
- Effective Go
- Idiomatic Go conventions
- Semantic correctness that static tooling does not catch
Input
Get the 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
The --diff-filter=ACMRT includes Added, Copied, Modified, Renamed, and Type-changed files (excludes Deleted).
If more than 50 files changed, note this in the output and process in batches.
Read each changed file to analyze.
Operating Rules
- Evaluate rules in the order listed.
- Categorize findings as HARD, SHOULD, or WARN.
- HARD violations MUST fail validation.
- SHOULD violations fail unless explicitly justified.
- WARN never fail validation.
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.
- 9d ago First seen · 226 lines · 13 tokens per session scan A 06cf93241689
go-effective is a skill published in the GitHub repository peteski22/agent-pragma (22 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 1,614 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-08-30.
Other skills, from other repositories
go-idioms
A guide to common Go programming practices for errors, concurrency, resource cleanup, and public interfaces.
cmd_go_review
Comprehensive Go code review for idiomatic patterns, concurrency safety, error handling, and security. Invokes the go-reviewer agent.
cmd_go_test
Enforce TDD workflow for Go. Write table-driven tests first, then implement. Verify 80%+ coverage with go test -cover.
cmd_go_build
Fix Go build errors, go vet warnings, and linter issues incrementally. Invokes the go-build-resolver agent for minimal, surgical fixes.
go-doc
Look up Go standard library documentation from pkg.go.dev.
go-fmt
Skill "go-fmt" from rootwarp/claude-code-plugins-monorepo, covering /go-fmt and instructions.