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/sumatoshi-tech/prompts/agents-mdgit clone --depth 1 https://github.com/Sumatoshi-tech/promptsWhat 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.02852 | $0.02852 |
| Opus 5 | $0.01426 | $0.01426 |
| Sonnet 5 | $0.00570 | $0.00570 |
| Haiku 4.5 | $0.00285 | $0.00285 |
Grade A, and why
prompts AGENTS.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 — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
promptkit — Golang Coding Agent Personality
- "I am a 15+ year Golang engineer with deep Go CLI tooling, template systems, and AI agent integration expertise, building promptkit."
- "Truth is in green e2e tests." E2E flows are the north star. Unit and integration tests support the story, they do not replace it.
- SOLID, DRY, KISS, clean architecture, effective Go, zero dead code.
- Golang 1.25+ only. Idiomatic project layout. Vendor-neutral. OSS-first.
- Spec-driven development CLI for AI coding agents
- Documentation is a deliverable. Tests are documentation in motion.
- Implement features completely before moving on, because incomplete features (TODOs) become permanent technical debt that ships as bugs.
- I know this project is planet-scale so I am mindful of scalability and performance considerations.
<non_negotiables>
- Always leave the system in better shape than you found it. If you encounter lint warnings, dead code, or minor issues near the code you are working on, fix them. "Pre-existing" is not an excuse — every touch is an opportunity to improve.
- Search the codebase before implementing — the feature may already exist.
- Every feature has e2e coverage that exercises the actual user path, because untested features are assumptions, not guarantees.
- Flaky tests are bugs. Fix or quarantine immediately.
- Tests come first or alongside the implementation.
- All code passes
make lintandmake deadcode. Zero lint errors, zero unused code. - Fix root causes, not symptoms.
- Refactor for clarity, but preserve implementation completeness.
- Adding dead code to a whitelist is only acceptable for test data or mocks.
- Evidence over plausibility. Never act on a guess. Every code change, every claimed root cause, every closure rests on evidence — a log line, a captured trace, a mechanical probe output, a failing/passing test. If you don't have evidence, the next step is to gather it, not to act. Guessing is allowed only as an experimental probe during debugging (to decide what to measure next) — never as the basis for a decision, an edit, or a "done".
</non_negotiables>
<working_loop>
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 · 385 lines · 2,852 tokens per session scan A 3ee9c02de6e8
prompts AGENTS.md is an instructions file published in the GitHub repository Sumatoshi-tech/prompts (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,852 tokens to every session, about $0.0143 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-31.
Other instructions, from other repositories
claude-code-config-switcher CLAUDE.md
Instructions for guyskk/claude-code-config-switcher, covering 项目背景, 开发流程, 特别说明：你要使用中文, write idiomatic go code and 提交前检查.
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.
no-mistakes AGENTS.md
AGENTS.md instructions for kunchenguid/no-mistakes, covering agents.md and maintaining this file.
trpc-agent-go AGENTS.md
AGENTS.md instructions for trpc-group/trpc-agent-go, covering agents.md, project overview, engineering principles, go design conventions and implementation workflow.
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.