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.
git 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/rules/chatbotgang/ai-coding-workshop-250712/go)<a href="https://agentmods.dev/rules/chatbotgang/ai-coding-workshop-250712/go"><img src="https://agentmods.dev/badge/rules/chatbotgang/ai-coding-workshop-250712/go/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.
<a href="https://agentmods.dev/rules/chatbotgang/ai-coding-workshop-250712/go"><img src="https://agentmods.dev/badge/rules/chatbotgang/ai-coding-workshop-250712/go.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.04191 |
| Opus 5.5 | $0.00000 | $0.01676 |
| Sonnet 5.5 | $0.00000 | $0.00838 |
| Haiku 4.5 | $0.00000 | $0.00419 |
Grade A, and why
go 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.
How it starts
The opening of the file, as written. The whole thing — 597 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.
- 1mo ago First seen · 597 lines · 4,191 tokens per session scan A 91e6a1927f14
go is a cursor rule published in the GitHub repository chatbotgang/ai-coding-workshop-250712 (65 stars, last pushed 1y ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,191 tokens. 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 cursor rules, from other repositories
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
code-style
Formatting, lint, comments language.
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
05-go-helpers
In a module whose go.mod requires x/rkit, use rkit before writing a small helper. Task → helper map and edge cases: x/rkit/README.md.