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.
npx agentmods add instructions/bigkevmcd/go-configparser/copilot-instructionsgit clone --depth 1 https://github.com/bigkevmcd/go-configparserWhat 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 | $0.01673 | $0.01673 |
| Opus 5 | $0.00837 | $0.00837 |
| Sonnet 5 | $0.00335 | $0.00335 |
| Haiku 4.5 | $0.00167 | $0.00167 |
Grade A, and why
go-configparser copilot-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 yesterday.
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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
go-configparser Development Instructions
ALWAYS follow these instructions first and only fallback to additional search and context gathering if the information here is incomplete or found to be in error.
go-configparser is a Go library that implements a Python ConfigParser-compatible configuration file parser with support for interpolation, custom options, and all major ConfigParser features.
Quick Start & Validation
Bootstrap and validate the repository with these commands:
go version-- ensure Go 1.21+ is installedgo build -v ./...-- builds in ~7 seconds, NEVER CANCELgo test -v ./...-- runs in ~5 seconds with 93.1% test coverage, NEVER CANCELgo test -cover ./...-- shows test coverage statistics
Essential Development Commands
Building
go build -v ./...-- build all packages (7 seconds)go build-- build current package only
Testing
go test -v ./...-- run all tests with verbose output (5 seconds)go test -cover ./...-- run tests with coverage reportgo test ./chainmap-- run tests for chainmap subpackage onlygo test -check.f TestSpecificFunction-- run specific test (uses check framework)
Code Quality
go vet ./...-- static analysis, runs instantlygofmt -l .-- check code formatting, runs instantlygo mod tidy-- clean up module dependencies~/go/bin/golangci-lint run-- comprehensive linting (install first with:go install github.com/golangci/golangci-lint/cmd/golangci-lint@latest, takes ~2 minutes to install)
CRITICAL: Always run before committing
go build -v ./...-- ensure code buildsgo test -v ./...-- ensure tests passgo vet ./...-- static analysisgofmt -l .-- verify formatting (should return no output)
Validation Scenarios
ALWAYS test functionality after making changes by running this validation scenario:
- Create a test program to validate core functionality:
package main
import (
"fmt"
"log"
"github.com/bigkevmcd/go-configparser"
)
func main() {
// Test parsing the example configuration file
p, err := configparser.NewConfigParserFromFile("testdata/example.cfg")
if err != nil {
log.Fatal(err)
}
// Test basic functionality
sections := p.Sections()
fmt.Printf("Sections: %v\n", sections)
// Test getting a value
value, err := p.Get("follower", "FrobTimeout")
if err != nil {
log.Fatal(err)
}
fmt.Printf("FrobTimeout: %s\n", value)
// Test interpolation
interpolated, err := p.GetInterpolated("follower", "builder_command")
if err != nil {
log.Fatal(err)
}
fmt.Printf("Interpolated: %s\n", interpolated)
fmt.Println("✓ Working correctly!")
}
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.
- yesterday First seen · 190 lines · 1,673 tokens per session scan A df6b0fcb5dbd
go-configparser copilot-instructions.md is an instructions file published in the GitHub repository bigkevmcd/go-configparser (30 stars, last pushed 10d ago), licensed MIT. It adds 1,673 tokens to every session, about $0.0084 per session on Opus 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-01.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.