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/nabinno/dojo/claude-mdgit clone --depth 1 https://github.com/nabinno/dojoWrote 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/nabinno/dojo/claude-md)<a href="https://agentmods.dev/instructions/nabinno/dojo/claude-md"><img src="https://agentmods.dev/badge/instructions/nabinno/dojo/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.01073 | $0.01073 |
| Opus 5 | $0.00536 | $0.00536 |
| Sonnet 5 | $0.00215 | $0.00215 |
| Haiku 4.5 | $0.00107 | $0.00107 |
Grade A, and why
dojo 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Repository Overview
This is a comprehensive coding practice and learning repository called "Nab's dojo" containing exercises and implementations across multiple programming languages, platforms, and technologies.
Build and Test Commands
Go Projects
Go projects use Ginkgo/Gomega BDD testing framework. All Go projects have similar structure:
# Navigate to any Go project directory (a_tour_of_go, atcoder, codewars, leetcode, project_euler)
cd <go_project_directory>
# Run tests
go test
# Run with verbose output
ginkgo -v
# Build
go build
AWS Lambda Project
Complex project with both Go Lambda functions and TypeScript CDK infrastructure:
cd aws_lambda
# Build all (Go lambdas + TypeScript CDK)
npm run build
# Build only Go lambdas
npm run build:go
# Build only TypeScript
npm run build:ts
# Run tests
npm test
# Deploy infrastructure
npm run deploy
# Local Lambda invocation (requires AWS SAM)
npm run invoke -- <function_name> <event_type>
AWS CDK Projects
cd aws_cdk/cdk-workshop
# Build TypeScript
npm run build
# Watch mode
npm run watch
# Run tests
npm test
# CDK commands
npm run cdk diff
npm run cdk deploy
DataCamp Python Projects
Uses Poetry for dependency management:
cd datacamp
# Install dependencies
poetry install
# Activate virtual environment
poetry shell
# Run Python scripts or notebooks
python <script_name>.py
Haskell Project (lyhgg)
cd lyhgg
# Build with Cabal
cabal build
# Run tests
cabal test
# Run executable
cabal run
Code Architecture
Go Projects Structure
- Each algorithmic challenge directory follows same pattern:
<name>.go- main implementation file<name>_suite_test.go- BDD test suite using Ginkgo/Gomegago.mod- Go module definition with dependencies
- All Go projects target Go 1.12
- Tests use descriptive BDD-style descriptions with nested contexts
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 · 166 lines · 1,073 tokens per session scan A fbd314a310ea
dojo CLAUDE.md is an instructions file published in the GitHub repository nabinno/dojo (58 stars, last pushed 2d ago), licensed MIT. It adds 1,073 tokens to every session, about $0.0054 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
dingtalk-workspace-cli AGENTS.md
AGENTS.md instructions for DingTalk-Real-AI/dingtalk-workspace-cli, covering repository agent guide, build and test, command framework declaration, flag / help / schema homology and agent schema contract.
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.
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).
agentcat-go-sdk CLAUDE.md
Claude Code instructions for agentcathq/agentcat-go-sdk, covering claude.md, what this is, build & test commands, module layout and architecture.
oastools GEMINI.md
Instructions for erraggy/oastools, covering gemini.md, project overview, building and running, key commands and development conventions.