gocode: Instructions file for Kiro

.kiro/steering/development-workflow.md

gocode development-workflow.md is an instructions file for Kiro from AlleyBo55/gocode. It costs 664 tokens per session, scanned A, original, MIT.

A development workflow guide for gocode, covering how to build the program, run tests, use the race detector, run benchmarks and static checks, and add tools or model providers.

In plain words
What is it for?
Use it when building or testing gocode, checking concurrent code, adding a tool, adding a provider, or locating project directories.
Why use it?
It replaces guesswork about project commands and required files. It helps contributors validate changes and follow the repository's process for extending the program.

Instructions file for Kiro

Written for Kiro: installed under .kiro/. Also seen: mentions CLAUDE.md.

This is AlleyBo55/gocode's own configuration. It tells Kiro how to work on gocode itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gocode configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is go build -o gocode ./cmd/gocode/.

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/development-workflow.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.

agentmods badge for gocode development-workflow.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/alleybo55/gocode/development-workflow/github.svg)](https://agentmods.dev/instructions/alleybo55/gocode/development-workflow)
Your own site
<a href="https://agentmods.dev/instructions/alleybo55/gocode/development-workflow"><img src="https://agentmods.dev/badge/instructions/alleybo55/gocode/development-workflow/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.

agentmods 80×15 button for gocode development-workflow.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/alleybo55/gocode/development-workflow"><img src="https://agentmods.dev/badge/instructions/alleybo55/gocode/development-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 664 This file is loaded in full into every session.
When invoked 664 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00664 $0.00664
Opus 5.5 $0.00266 $0.00266
Sonnet 5 $0.00133 $0.00133
Haiku 4.5 $0.00066 $0.00066

Measured 2d ago against content hash 06a99047fa0b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-27, from the pricing page.

Security

Grade A, and why

gocode development-workflow.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 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.

.kiro/steering/development-workflow.md · 101 lines

How it starts

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

Development Workflow — gocode

Build & Test

# Build
go build -o gocode ./cmd/gocode/

# Test all packages
go test ./...

# Test specific package
go test ./internal/agent/...

# Test with race detector
go test -race ./...

# Benchmark
go test -bench=. ./internal/toolimpl/

# Vet
go vet ./...

Project Layout

cmd/gocode/main.go       — CLI entrypoint, all Cobra commands, wiring
internal/                — All business logic (26 packages)
data/                    — Embedded JSON registries (go:embed)
docs/                    — User-facing documentation
.gocode/                 — Runtime config (skills, hooks, cron, themes)

Adding a New Tool

  1. Create executor in internal/toolimpl/:
type MyNewTool struct{}

func (t *MyNewTool) Execute(params map[string]interface{}) ToolResult {
    // implementation
    return ToolResult{Success: true, Output: "done"}
}
  1. Register in NewRegistry():
r.executors["mynewtool"] = &MyNewTool{}
  1. Add tool definition to data/tools.json with name, description, inputSchema.

  2. Write tests in internal/toolimpl/toolimpl_test.go.

Adding a New Provider

  1. Implement Provider interface in internal/apiclient/.
  2. Add resolution logic in ResolveProvider().
  3. Add model aliases in internal/apiclient/aliases.go.
  4. Document in docs/supported-models.md.

Adding a New Slash Command

  1. Add handler in internal/repl/repl.go in the slash command switch.
  2. Add to help text.
  3. Document in docs/ux-features.md.

Git Conventions

  • Atomic commits. One logical change per commit.
  • Commit messages: imperative mood, 50 char subject, blank line, body if needed.
  • Branch naming: feat/short-description, fix/short-description, refactor/short-description.
  • Always run go test ./... before committing.
  • Use /review to self-review before pushing.

Configuration Files

File Purpose
GOCODE.md / CLAUDE.md Project-specific agent instructions
.gocode/skills/*.json Custom skill definitions
.gocode/hooks.json Lifecycle hooks
.gocode/cron.json Scheduled tasks
.gocode/mcp.json MCP client server configs
.gocode/theme.json Custom TUI theme
.gocode/keybinds.json Custom keybindings
.gocode/output-styles/ Custom output styles

Read the full file on GitHub · 101 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.

  1. 2d ago First seen · 101 lines · 664 tokens per session scan A 06a99047fa0b

Subscribe to this mod's changes

gocode development-workflow.md is an instructions file published in the GitHub repository AlleyBo55/gocode (46 stars, last pushed 3d ago), licensed MIT. It adds 664 tokens to every session, about $0.0027 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.

Related

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

microsoft/vscode · 9,406 tokens

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.

vercel/next.js · 6,985 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

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

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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

microsoft/vscode · 2,494 tokens