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/guyskk/claude-code-config-switcher/claude-mdgit clone --depth 1 https://github.com/guyskk/claude-code-config-switcherWrote 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/guyskk/claude-code-config-switcher/claude-md)<a href="https://agentmods.dev/instructions/guyskk/claude-code-config-switcher/claude-md"><img src="https://agentmods.dev/badge/instructions/guyskk/claude-code-config-switcher/claude-md.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.01305 | $0.01305 |
| Opus 5 | $0.00652 | $0.00652 |
| Sonnet 5 | $0.00261 | $0.00261 |
| Haiku 4.5 | $0.00130 | $0.00130 |
Grade A, and why
claude-code-config-switcher CLAUDE.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 5d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
项目背景
具体内容见 @README.md(必读)
开发流程
本项目使用 TDD 开发流程,你要根据具体需求,用 /test-driven-development 按流程完成开发任务。
特别说明:你要使用中文
我的母语是中文,你要用中文和我沟通,这样更方便。
Write idiomatic Go code
Write idiomatic Go code with goroutines, channels, and interfaces. Optimizes concurrency, implements Go patterns, and ensures proper error handling. Use PROACTIVELY for Go refactoring, concurrency issues, or performance optimization.
When write code:
- Analyze requirements and design idiomatic Go solutions
- Implement concurrency patterns using goroutines, channels, and select
- Create clear interfaces and struct composition patterns
- Establish comprehensive error handling with custom error types
- Set up testing framework with table-driven tests and benchmarks
- Optimize performance using pprof profiling and measurements
Process:
- Prioritize simplicity first - clear is better than clever
- Apply composition over inheritance through well-designed interfaces
- Implement explicit error handling with no hidden magic
- Design concurrent systems that are safe by default
- Benchmark thoroughly before optimizing performance
- Prefer standard library solutions over external dependencies
- Follow effective Go guidelines and community best practices
- Organize code with proper module management and clear package structure
Provide:
- Idiomatic Go code following effective Go guidelines and conventions
- Concurrent code with proper synchronization and race condition prevention
- Table-driven tests with subtests for comprehensive coverage
- Benchmark functions for performance-critical code paths
- Error handling with wrapped errors, context, and custom error types
- Clear interfaces and struct composition patterns
- go.mod setup with minimal, well-justified dependencies
- Performance profiling setup and optimization recommendations
提交前检查
Usage: ./check.sh [OPTIONS]
Options:
-l, --lint Run lint checks (gofmt, go vet, shellcheck, markdownlint)
-t, --test Run tests with race detector
-b, --build Run build validation
-h, --help Show this help message
If no options specified, runs all checks (lint, test, build).
Examples:
./check.sh # Run all checks
./check.sh --lint # Run lint only
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.
- 5d ago First seen · 165 lines · 1,305 tokens per session scan A b8326e0962cf
claude-code-config-switcher CLAUDE.md is an instructions file published in the GitHub repository guyskk/claude-code-config-switcher (85 stars, last pushed 2mo ago), licensed MIT. It adds 1,305 tokens to every session, about $0.0065 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-08-30.
Other instructions, from other repositories
prompts AGENTS.md
Instructions for Sumatoshi-tech/prompts, covering promptkit — golang coding agent personality, working loop, micro-tdd development flow, e2e testing philosophy and architecture preferences.
copilot-tdd-harness tdd-patterns.instructions.md
Go-specific TDD conventions for this repository, including test naming, commands, and test-double guidance.
gitlab-mcp CLAUDE.md
Instructions for wadew/gitlab-mcp, covering claude code development guide - gitlab mcp server, ground rules, test-driven development (tdd) - mandatory, code coverage requirements and phase gate criteria.
unraid-management-agent copilot-instructions.md
Copilot instructions for ruaan-deysel/unraid-management-agent, covering copilot instructions, copilot workflow, path-specific instructions, reusable prompts and quick commands.
coral CLAUDE.md
Instructions for cdknorow/coral, covering claude.md - coral go, mission, testing, go unit tests and legacy parity tools (historical reference).
oastools GEMINI.md
Instructions for erraggy/oastools, covering gemini.md, project overview, building and running, key commands and development conventions.