Go安全规范

Go coding rules for safer handling of secrets, input, environment variables, and operations that may wait. They also specify using gosec, a tool that scans Go code for common security issues.

In plain words
What is it for?
Use them when building or reviewing Go services, especially code that reads environment variables or calls external services, databases, or remote procedures.
Why use it?
They help catch unsafe code and prevent missing configuration, leaked resources, or calls that wait forever.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/nongjun/awesome-harness-engineering/go
Clone the repo
git clone --depth 1 https://github.com/nongjun/awesome-harness-engineering
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 167 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00167
Opus 5 $0.00000 $0.00084
Sonnet 5 $0.00000 $0.00033
Haiku 4.5 $0.00000 $0.00017

Measured 2d ago against content hash 6bba0e095765, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

rules/Go安全规范.mdc · 21 lines

What it actually says

Go 安全

密钥管理、输入验证等通用规范见安全红线。

安全扫描

  • 使用 gosec 做静态安全分析:gosec ./...

环境变量

读取后校验非空,缺失时明确失败(记录或退出),不得静默继续。

Context 与超时

对外部调用、RPC、数据库等可能阻塞的操作,一律通过 context.Context 传递;需要上限时,在调用链上设置合理超时并在结束时取消,避免泄漏与无限等待。

Changes

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.

  1. 2d ago First seen · 21 lines · 0 tokens per session scan A 6bba0e095765

Subscribe to this mod's changes

Go安全规范 is a cursor rule published in the GitHub repository nongjun/awesome-harness-engineering (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 167 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.