What is gocode go-engineering.md?

Go engineering instructions for gocode, an AI coding agent written in Go. They cover package structure, concurrency, errors, naming, formatting, static checks, and project-specific implementation patterns.

Use them when writing or reviewing Go code in gocode, especially code involving packages, concurrency, interfaces, persistence, and error handling.

They give contributors one set of rules for keeping the codebase consistent and reducing common Go defects. They also define checks such as `gofmt`, `go vet`, and error wrapping.

How AlleyBo55/gocode configures Kiro

Reuse

Borrowing it

Nothing to install: this file belongs to AlleyBo55/gocode. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/AlleyBo55/gocode/master/.kiro/steering/go-engineering.md

Clone the repo

git clone --depth 1 https://github.com/AlleyBo55/gocode

Made for: Kiro.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/alleybo55/gocode/go-engineering/github.svg)](https://agentmods.dev/instructions/alleybo55/gocode/go-engineering)

Your own site

<a href="https://agentmods.dev/instructions/alleybo55/gocode/go-engineering"><img src="https://agentmods.dev/badge/instructions/alleybo55/gocode/go-engineering/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/alleybo55/gocode/go-engineering"><img src="https://agentmods.dev/badge/instructions/alleybo55/gocode/go-engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 845 This file is loaded in full into every session.

When invoked 845 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00845	$0.00845
Opus 5.5	$0.00338	$0.00338
Sonnet 5.5	$0.00169	$0.00169
Haiku 4.5	$0.00085	$0.00085

Measured 1mo ago against content hash 253e327a1316, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gocode go-engineering.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.

.kiro/steering/go-engineering.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Go Engineering Standards — gocode

You are working on gocode, a high-performance AI coding agent written in Go. Single binary, zero runtime dependencies, 26 internal packages, 200+ model support across 11 providers.

Architecture Principles

Every package owns its interface. No god objects. No circular imports.
Concurrency via goroutines + channels. Never share memory without a channel or sync primitive.
(T, error) everywhere. No panics in library code. Panics are bugs.
Interfaces are small (1-3 methods). Accept interfaces, return structs.
go:embed for compiled-in data. No runtime file reads for registries.
Atomic file writes (temp + rename) for all persistence. Zero corruption guarantee.

Code Style

Follow gofmt and go vet unconditionally. No exceptions.
Naming: camelCase for unexported, PascalCase for exported. No underscores in Go identifiers.
Package names are short, lowercase, singular nouns: agent, session, repl, not agents, sessions.
Error messages start lowercase, no trailing punctuation: return fmt.Errorf("loading config: %w", err)
Wrap errors with %w for the chain. Use errors.Is / errors.As for checking.
Comments on exported symbols are mandatory. Start with the symbol name: // NewRegistry creates...
Table-driven tests. Subtests with t.Run. No test helpers that hide assertions.
Keep functions under 50 lines. If it's longer, extract a helper.

Project-Specific Patterns

Tool implementations go in internal/toolimpl/ and implement the ToolExecutor interface.
Provider implementations go in internal/apiclient/ and implement the Provider interface.
New CLI subcommands are added in cmd/gocode/main.go using Cobra.
Skills are JSON files in .gocode/skills/ with name, system_prompt, tool_permissions.
The ConversationRuntime in internal/agent/runtime.go is the core agent loop — understand it before touching agent behavior.
The FallbackProvider and ModelRouter in internal/apiclient/ handle model routing and failover.
Session persistence uses internal/session/ with atomic writes.
The orchestrator in internal/orchestrator/ manages sub-agents with independent goroutines.

Read the full file on GitHub · 72 lines

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.

1mo ago First seen · 72 lines · 845 tokens per session scan A 253e327a1316

Subscribe to this mod's changes

gocode go-engineering.md is an instructions file published in the GitHub repository AlleyBo55/gocode (48 stars, last pushed 6d ago), licensed MIT. It adds 845 tokens to every session, about $0.0034 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-09-25.

Claude Code Code review Languages ai ai-agents ai-tools cli code-cli

gocode go-engineering.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
gocode go-engineering.mdAlleyBo55/gocode	Instructions file	48	6d ago	MIT	A	845	Kiro
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,685	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	279k	today	MIT	A	4,325	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,086	GitHub Copilot

gocode: Instructions file for Kiro