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 Goldziher/ai-rulez --skill go-conventionsgit clone --depth 1 https://github.com/Goldziher/ai-rulezWrote 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/goldziher/ai-rulez/go-conventions)<a href="https://agentmods.dev/skills/goldziher/ai-rulez/go-conventions"><img src="https://agentmods.dev/badge/skills/goldziher/ai-rulez/go-conventions/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/goldziher/ai-rulez/go-conventions"><img src="https://agentmods.dev/badge/skills/goldziher/ai-rulez/go-conventions.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.00047 | $0.00399 |
| Opus 5 | $0.00023 | $0.00199 |
| Sonnet 5 | $0.00009 | $0.00080 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
go-conventions 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 11d 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.
What it actually says
- Follow Effective Go and Go Code Review Comments guidelines.
- Handle every error return. Wrap errors with context:
fmt.Errorf("operation failed: %w", err). - Linting: a meta-linter (e.g., golangci-lint) with strict config (enable
govet,staticcheck,errcheck, and a security analyzer). Format withgofmt/goimports. - Security:
govulncheckfor CVE scanning, a SAST tool for static analysis. Run both in CI. - Testing: table-driven tests with
t.Run()and the stdlibtestingpackage. Uset.Parallel()where safe. An assertion library (e.g., testify) is optional. Coverage withgo test -coverprofile. - Naming: use short, descriptive names. Receivers are 1-2 letters. Exported names are descriptive.
- Prefer composition over inheritance. Use interfaces for abstraction (accept interfaces, return structs).
- Keep packages small and focused. Avoid package-level state and
init()functions. - Use
context.Contextas first parameter for cancelable operations. Never store contexts in structs. - Error types: use
errors.Is()/errors.As()for comparison. Define sentinel errors witherrors.New(). - Modules: use Go modules. Commit
go.sum. Use semantic version tags. Prefer stdlib over third-party when reasonable. - Concurrency: prefer channels over mutexes. Use
sync.WaitGroupfor fan-out. Guard shared state. - Benchmarking: use
testing.Bbenchmarks. Profile withgo tool pprof. Usebenchstatfor comparison.
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.
- 11d ago First seen · 19 lines · 47 tokens per session scan A e0fe81ec2126
go-conventions is a skill published in the GitHub repository Goldziher/ai-rulez (141 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 399 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-30.
Other skills, from other repositories
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
vhs-e2e-gif
Record a test run, a TUI session, or any terminal command as a GIF with VHS and attach it to a GitHub PR as a release-hosted asset, never a repo commit. Use when asked to record an e2e run, demo a fix on a PR, attach a GIF or screen recording to a pull request, show a test passing visually, or produce a terminal…
pixiv-cli-review
Review pixiv-cli worktree, commit range, or GitHub pull request for architectural boundaries, public CLI/MCP/SDK contracts, security, documentation obligations, tests, and workflow policy. Use for code review, PR review, pre-release review, or review of agent/workflow changes.
code-review-pi
Review code for quality, run linters, check test coverage, fix issues, and enforce gates. Save the final report to ./specs/issues/003-code-review-pi/PROMPT.md. Use before committing changes.
printing-press-output-review
Internal sub-skill: agentic review of a printed CLI's sampled command output for plausibility issues that rule-based checks can't encode (substring-match relevance, format bugs, silent source drops, ranking failures). Invoked via the Skill tool by the main printing-press skill at Phase 4.85 and printing-press-polish…
review-work
Post-implementation review orchestrator. Launches 5 parallel background sub-agents: Oracle (goal/constraint verification), Oracle (code quality), Oracle (security), unspecified-high (hands-on QA execution), unspecified-high (context mining from GitHub/git/Slack/Notion). All must pass for review to pass. MUST USE…