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/nrdxp/predicate/gonpx skills add nrdxp/predicate --skill gogit clone --depth 1 https://github.com/nrdxp/predicateWhat 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.00112 | $0.01941 |
| Opus 5 | $0.00056 | $0.00971 |
| Sonnet 5 | $0.00022 | $0.00388 |
| Haiku 4.5 | $0.00011 | $0.00194 |
Grade A, and why
go 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 2d 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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Language Idioms
Go favors simplicity, readability, and explicit behavior. Work with the language's conventions, not against them.
Core Philosophy
- Simplicity over cleverness — clear, boring code is better than clever, obscure code
- Explicit over implicit — errors are values, not exceptions
- Composition over inheritance — embed types, implement interfaces
- Share by communicating — don't communicate by sharing memory
Formatting
Let gofmt handle it. Don't fight the formatter.
gofmt -w . # Format all files
go fmt ./... # Format package
All Go code in the ecosystem follows gofmt. There is no debate.
Naming
General Rules
| Scope | Style | Example |
|---|---|---|
| Exported | PascalCase |
ReadFile, HTTPClient |
| Unexported | camelCase |
readFile, httpClient |
| Packages | lowercase, single word | bytes, http, bufio |
| Acronyms | All caps | HTTP, URL, ID (not Http, Url, Id) |
Package Names
- Short, concise, evocative
- No underscores or mixedCaps
- The package name is part of the type name:
bufio.Reader, notbufio.BufReader
Getters and Setters
// ❌ Don't prefix getters with "Get"
func (u *User) GetName() string
// ✅ Just use the field name
func (u *User) Name() string
// ✅ Setters use "Set" prefix
func (u *User) SetName(name string)
Interface Names
One-method interfaces use method name + -er suffix:
| Method | Interface |
|---|---|
Read |
Reader |
Write |
Writer |
Close |
Closer |
String |
Stringer |
Functions
Multiple Return Values
Go functions return (result, error) instead of throwing:
func ReadFile(path string) ([]byte, error) {
f, err := os.Open(path)
if err != nil {
return nil, err
}
defer f.Close()
return io.ReadAll(f)
}
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.
- 2d ago First seen · 337 lines · 112 tokens per session scan A d79adbe018b5
go is a skill published in the GitHub repository nrdxp/predicate (10 stars, last pushed 8d ago), licensed MIT. It adds 112 tokens to every session and 1,941 once invoked, about $0.0006 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…