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/chatbotgang/ai-coding-workshop-250712/gogit clone --depth 1 https://github.com/chatbotgang/ai-coding-workshop-250712Wrote 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/chatbotgang/ai-coding-workshop-250712/go)<a href="https://agentmods.dev/instructions/chatbotgang/ai-coding-workshop-250712/go"><img src="https://agentmods.dev/badge/instructions/chatbotgang/ai-coding-workshop-250712/go.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 | $0.04161 | $0.04161 |
| Opus 5 | $0.02080 | $0.02080 |
| Sonnet 5 | $0.00832 | $0.00832 |
| Haiku 4.5 | $0.00416 | $0.00416 |
Grade A, and why
ai-coding-workshop-250712 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 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.
How it starts
The opening of the file, as written. The whole thing — 596 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Development Guide in CL
This document provides comprehensive guidance for Go development in Crescendo Lab, covering architecture patterns, coding style, and best practices.
Table of Contents
- Architecture Patterns
- Package Structure
- Code Organization
- Naming Conventions
- Types and Structs
- Functions and Methods
- Error Handling
- Concurrency
- Testing
- Performance Considerations
- Logging and Observability
- Documentation
- Project Structure
Architecture Patterns
Clean Architecture
Go project in CL follows a clean architecture pattern with distinct layers:
-
Domain Layer (
internal/domain/)- Contains business entities and logic
- Independent of external frameworks and databases
- Defines interfaces that are implemented by outer layers
-
Application Layer (
internal/app/)- Contains application services that orchestrate domain entities
- Implements use cases of the system
- Depends on domain layer, but not on external frameworks
-
Adapter Layer (
internal/adapter/)- Implements interfaces defined in the domain layer
- Connects the application to external systems (databases, message brokers, etc.)
- Contains concrete implementations of repositories and services
-
Router Layer (
internal/router/)- Entry points to the application (HTTP handlers, CLI commands)
- Depends on application services
- Translates external requests to internal application calls
Common Patterns
Interface Design
- Define interfaces in the layer that uses them, not in the layer that implements them
- Keep interfaces small and focused on a single responsibility
- Use dependency injection to provide implementations
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.
- 2d ago First seen · 596 lines · 4,161 tokens per session scan A d32daa2c6768
ai-coding-workshop-250712 go.instructions.md is an instructions file published in the GitHub repository chatbotgang/ai-coding-workshop-250712 (66 stars, last pushed 1y ago), licensed Apache-2.0. It adds 4,161 tokens to every session, about $0.0208 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
go-micro CLAUDE.md
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.
no-mistakes AGENTS.md
AGENTS.md instructions for kunchenguid/no-mistakes, covering agents.md and maintaining this file.
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 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.
mcp-go AGENTS.md
Instructions for mark3labs/mcp-go, covering commands, git and code style.
stackql AGENTS.md
Instructions for stackql/stackql, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.