Borrowing it
Nothing to install: this file belongs to azrtydxb/procoder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/azrtydxb/procoder/main/.github/instructions/go.instructions.mdgit clone --depth 1 https://github.com/azrtydxb/procoderWrote 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/instructions/azrtydxb/procoder/go)<a href="https://agentmods.dev/instructions/azrtydxb/procoder/go"><img src="https://agentmods.dev/badge/instructions/azrtydxb/procoder/go/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/instructions/azrtydxb/procoder/go"><img src="https://agentmods.dev/badge/instructions/azrtydxb/procoder/go.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.00924 | $0.00924 |
| Opus 5.5 | $0.00370 | $0.00370 |
| Sonnet 5.5 | $0.00185 | $0.00185 |
| Haiku 4.5 | $0.00092 | $0.00092 |
Grade A, and why
procoder go.instructions.md 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go in procoder
Procoder is a Go CLI plus an agent layer. cmd/procoder/main.go is the
dispatch and every domain lives under internal/<domain>/. The rules
below are not style preferences — each one is here because breaking it
produced a defect that shipped.
No silent green
The rule the whole tool is built on: a check that could not run must never read as one that passed.
- A tool that is absent, a file that could not be read, a scanner that crashed — each is reported as NOT checked, naming the reason, and it fails the gate exactly as a real finding would.
- Never return
nilfindings on an error path.if err != nil { return nil }is the shape that hides a whole domain. - An empty result is not a clean result. If a check scanned zero files, say so; do not print "0 finding(s)", which is what a clean scan prints.
- When a tool fails, quote its last line of stderr, not its first. Scanners log progress first and the reason they gave up last, so the first line produced "dependencies were NOT checked: Starting filesystem walk for root: /" — alarming, and not the reason. Fall back to the exit status only when stderr is empty.
P-CONTROL: the binary prints, the agent writes
No command may modify a file in the repository it is checking.
procoder format prints the formatted result for review. The one
exception is procoder's own state under .procoder/, written by
controllers that say so, and --save/--yes flags where writing is the
whole point of the flag.
Paths and arguments
- A command taking paths must honour them.
procoder security <dir>scanned the change set and ignored its argument, so a person who named a directory was told "0 finding(s)" about files nobody opened. - Expand a directory argument to its files. Checks that work file by file silently do nothing with an unexpanded directory.
- Resolve relative paths against the repository root, not the process
directory — procoder can be run from a subdirectory, and
gitx.ChangedFileshands out absolute paths, so mixing the two makes a check scan nothing. - A flag a command does not implement is a usage error (exit 2), never a
path. Every flag lives in
knownFlagsincmd/procoder/flags.go, and a test holds that table against the literals main.go compares.
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 · 88 lines · 924 tokens per session scan A 2c9912b095e7
procoder go.instructions.md is an instructions file published in the GitHub repository azrtydxb/procoder (211 stars, last pushed today), licensed Apache-2.0. It adds 924 tokens to every session, about $0.0037 per session on Opus 5.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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).