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/future-architect/uzomuzo-oss/copilot-instructionsgit clone --depth 1 https://github.com/future-architect/uzomuzo-ossWrote 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/future-architect/uzomuzo-oss/copilot-instructions)<a href="https://agentmods.dev/instructions/future-architect/uzomuzo-oss/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/future-architect/uzomuzo-oss/copilot-instructions.svg" alt="Measured on agentmods" 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.00724 | $0.00724 |
| Opus 5 | $0.00362 | $0.00362 |
| Sonnet 5 | $0.00145 | $0.00145 |
| Haiku 4.5 | $0.00072 | $0.00072 |
Grade A, and why
uzomuzo-oss 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 4d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions for Go
This project uses split instruction files for maintainability.
See .github/instructions/ for detailed rules.
Instruction Files
| File | Scope |
|---|---|
| language-policy | Source code English / docs English / response language |
| ddd-architecture | DDD layer definitions, search-first, pre-implementation checklist |
| coding-standards | Clean Code, naming, API design, goimports/golangci-lint |
| error-handling | Error wrapping (%w), errors.Is/As, slog integration |
| testing-performance | Table-driven tests, benchmarks, concurrency (how to write Go tests) |
| test-design | Pre-PR lens: classical QA techniques, fuzz/PBT policy, DDD layer placement (what to test) |
| project-conventions | Configuration policy, test data, JSON tooling constraints |
| git-workflow | Commit messages, PR workflow, runtime verification, TDD |
| security | Prompt injection defense, credentials, Go security |
| agent-orchestration | Available agents, usage rules, parallel execution |
Review Scope
When performing code review on pull requests, do not review or comment on Markdown files (*.md). Focus code review on Go source files, YAML workflows, and configuration files only.
Quick Reference
- Language: Source code = English only. Docs = English (
README.md,docs/*.md). Respond in the user's language. - DDD Layers:
Interfaces → Application → Domain ← Infrastructure. Never violate. - Search First: Always search for existing implementations before writing new code.
- Error Handling: Always wrap errors with
fmt.Errorf("context: %w", err). - Formatting: All Go code MUST be formatted with
goimports. - Configuration: Do NOT add new env vars / CLI flags casually. See project-conventions for checklist.
- Security: No hardcoded secrets. No
exec.Command("sh", "-c", userInput). - Testing: Table-driven tests,
t.Run()sub-tests, test with-raceflag.
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.
- 4d ago First seen · 46 lines · 724 tokens per session scan A ff2bfc18600c
uzomuzo-oss copilot-instructions.md is an instructions file published in the GitHub repository future-architect/uzomuzo-oss (32 stars, last pushed yesterday), licensed Apache-2.0. It adds 724 tokens to every session, about $0.0036 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
awesome-go AGENTS.md
AGENTS.md instructions for avelino/awesome-go, covering awesome-go · llm contribution guide, project snapshot, when modifying the awesome list, coding guidelines and testing & validation.
go-micro CLAUDE.md
Claude Code instructions for micro/go-micro, covering claude.md - go micro project guide, project overview, build & test, run all tests and run tests for a specific package.
azure-sdk-for-go go-examples.instructions.md
Instructions for Azure/azure-sdk-for-go, a project described as: This repository is for active development of the Azure SDK for Go. For consumers of the SDK we recommend visiting our public developer docs at.
azure-sdk-for-go copilot-instructions.md
Copilot instructions for Azure/azure-sdk-for-go, covering generated code — do not suggest changes, prerequisites, local sdk generation and package lifecycle (typespec), authoritative reference and default behaviors.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.
azure-sdk-for-go tsp-location.instructions.md
Instructions for Azure/azure-sdk-for-go, covering pre-requisites, regen and shortcuts.