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.
git clone --depth 1 https://github.com/perniemann/pnCoreWrote 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/rules/perniemann/pncore/pn-go-backend)<a href="https://agentmods.dev/rules/perniemann/pncore/pn-go-backend"><img src="https://agentmods.dev/badge/rules/perniemann/pncore/pn-go-backend/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/rules/perniemann/pncore/pn-go-backend"><img src="https://agentmods.dev/badge/rules/perniemann/pncore/pn-go-backend.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00740 |
| Opus 5.5 | $0.00000 | $0.00296 |
| Sonnet 5.5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
pn-go-backend 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go / backend rules
Error handling
- Check every returned error. Never discard with
_unless you have an explicit written reason. - Wrap errors with context using
fmt.Errorf("operation failed: %w", err). Useerrors.Isanderrors.Asfor comparison — never string-match error messages. - Define sentinel errors for expected failures:
var ErrNotFound = errors.New("not found"). Return these for known operational states. - Use
log/slog(Go 1.21+) for structured logging. Log errors at the level where recovery is decided, not at every call site.
Context
- Pass
context.Contextas the first parameter in all I/O functions:func FetchUser(ctx context.Context, id int64) (*User, error). - Respect context cancellation: check
ctx.Err()in loops and before expensive operations. - Never store context in structs. Never use
context.Background()inside a request handler — propagate the request context.
Naming and style
- Use short variable names in small scopes (
i,v,err) but descriptive names for exported types and functions. - Exported names are PascalCase; unexported are camelCase. Acronyms follow Go convention:
userID,httpClient,parseURL. - Interfaces belong in the package that uses them, not the package that implements them.
- Avoid
init()for side effects. Initialize dependencies explicitly inmainor constructors.
Secrets and config
- All config and secrets from environment variables (
os.Getenv). Never hardcode secrets in source. - Use
os.LookupEnvwhen a missing variable must be detected:val, ok := os.LookupEnv("DB_URL"); if !ok { log.Fatal("DB_URL required") }. - Consider
envconfigorviperfor structured config with validation at startup.
Goroutines and concurrency
- Every goroutine must have an owner responsible for its lifetime. Use
sync.WaitGroup,errgroup, or channel signaling. - Avoid goroutine leaks: goroutines that block on channels or I/O indefinitely. Use
context.WithTimeoutfor all external calls. - Prefer
errgroup.Groupover raw goroutines for parallel work that must be joined and checked for errors.
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 · 47 lines · 0 tokens per session scan A ceca5314c7f8
pn-go-backend is a cursor rule published in the GitHub repository perniemann/pnCore (0 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 740 tokens. 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 cursor rules, from other repositories
python--typescript-guide-cursorrules-prompt-file
Cursor rules for Python development with TypeScript guide integration.
nestjs-best-practices
../../.claude/rules/nestjs-best-practices.md.
backend-stack-rules
A set of rules for backend code using Next.js API Routes, TypeScript, Zod validation, optional authentication, and a project-selected database tool.
tsoa-rules
This document outlines comprehensive guidelines and best practices for developing Node.js server-side applications with tsoa, focusing on TypeScript for type safety and OpenAPI specification generation.
api-design-typescript
API Design for TypeScript — Express, NestJS, Fastify patterns, middleware, validation, and error handling. Extends core/rules/api-design.mdc with TypeScript-specific guidance.
typescript
Cursor rule "typescript" from girijashankarj/cursor-handbook, covering backend: typescript, strictness, types and conventions.