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/kbrdn1/gwm-cli/claude-mdgit clone --depth 1 https://github.com/kbrdn1/gwm-cliWrote 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/kbrdn1/gwm-cli/claude-md)<a href="https://agentmods.dev/instructions/kbrdn1/gwm-cli/claude-md"><img src="https://agentmods.dev/badge/instructions/kbrdn1/gwm-cli/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.02444 | $0.02444 |
| Opus 5 | $0.01222 | $0.01222 |
| Sonnet 5 | $0.00489 | $0.00489 |
| Haiku 4.5 | $0.00244 | $0.00244 |
Grade A, and why
gwm-cli 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 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.
This is a copy
89% identical to gwm-cli AGENTS.md — 11 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gwm-cli — house rules for AI assistants
This file is the project-level CLAUDE.md. Anything stated here OVERRIDES defaults and applies to every contribution made via an AI assistant in this repository.
🔴 Primordial rule — Test-Driven Development is mandatory
No production code lands without a failing test that pinned the behaviour down first. This is not a guideline, it is a hard merge requirement. PRs that add or change behaviour without tests are sent back, full stop.
The TDD loop (red → green → refactor)
- Red — write a failing test that captures the new behaviour or the bug you are fixing. Run it. It MUST fail for the right reason (assertion mismatch, not a compile error in unrelated code). Commit the test alone if it helps reviewers see the contract.
- Green — write the minimum production code to make the test pass. No extra branches, no speculative abstractions.
- Refactor — clean up while the tests are green. Re-run the full suite after every refactor step.
What counts as "behaviour"
Anything observable from outside the function under test:
- A new CLI subcommand, flag, or output format → end-to-end test in
tests/cli_binary.rsviaassert_cmd. - A new public function in
src/<module>.rs→ unit test intests/<module>_tests.rs. - A new bootstrap step (file copy, guard, no-symlink, command hook) →
integration test in
tests/bootstrap_tests.rsexercising it against atempfile::TempDir. - A libgit2 worktree operation → integration test in
tests/worktree_integration.rsusingtests/common::init_repo(). - A TUI state transition → state-machine test in
tests/tui_app_tests.rs(ratatui-free).
Exceptions (narrow, must be argued in the PR description)
The bar to skip a test is "the change is observably untestable from the public surface". Concretely:
- Pure formatting / typo fixes in user-facing strings → no test required if the string is incidental (a log line, a help blurb). If the string is asserted somewhere, update the assertion.
- Dependency bumps without behaviour change → CI green is the test.
- Comments-only changes → no test required.
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 · 179 lines · 2,444 tokens per session scan A 4f96538a0a54
gwm-cli CLAUDE.md is an instructions file published in the GitHub repository kbrdn1/gwm-cli (133 stars, last pushed today), licensed Apache-2.0. It adds 2,444 tokens to every session, about $0.0122 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to gwm-cli AGENTS.md, differing in 11 lines, and is treated as a copy.
Other instructions, from other repositories
openscreen AGENTS.md
AGENTS.md instructions for getopenscreen/openscreen, covering agents.md, setup commands, development principles, project layout and code style.
tabularis AGENTS.md
AGENTS.md instructions for TabularisDB/tabularis, covering agents.md, directives, gitnexus — code intelligence, always do and never do.
cs CLAUDE.md
Claude Code instructions for boyter/cs, covering claude.md, project overview, build & test commands, architecture and query pipeline (pkg/search/).
hana-developer-cli-tool-example command-documentation.instructions.md
Use when creating or updating CLI command documentation in docs/02-commands/. Generates comprehensive markdown files with Mermaid diagrams showing command flow, detailed parameter tables organized by category, syntax examples, and related commands.
hana-developer-cli-tool-example mcp-server-development.instructions.md
Use when creating or updating MCP (Model Context Protocol) server components. Enforces TypeScript patterns, JSON-RPC communication rules, tool/resource/prompt registration, and integration with CLI command metadata. Ensures MCP server follows protocol requirements and maintains consistency with the CLI infrastructure.
hana-developer-cli-tool-example route-development.instructions.md
Use when creating or updating route files in routes/. Enforces consistent structure, error handling, database connection management, internationalization, and integration with the Express server and CLI command infrastructure. Ensures routes follow established patterns for endpoint registration, response formatting…