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/badminton-apps/badman/agents-mdgit clone --depth 1 https://github.com/Badminton-Apps/badmanWrote 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/badminton-apps/badman/agents-md)<a href="https://agentmods.dev/instructions/badminton-apps/badman/agents-md"><img src="https://agentmods.dev/badge/instructions/badminton-apps/badman/agents-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.06240 | $0.06240 |
| Opus 5 | $0.03120 | $0.03120 |
| Sonnet 5 | $0.01248 | $0.01248 |
| Haiku 4.5 | $0.00624 | $0.00624 |
Grade A, and why
badman 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 today.
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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository guidance (Claude Code, Cursor, AI)
This file (AGENTS.md) is the single source of truth for AI-assisted development in this repo.
CLAUDE.md is a symbolic link to AGENTS.md in the repository root (CLAUDE.md → AGENTS.md). Tools that read either path see the same content. Edit AGENTS.md only—do not replace the symlink with a duplicate file, or Claude Code and Cursor will drift apart.
Environment Setup
Required for dev and AI-assisted scripts:
# pnpm is pinned via the packageManager field; corepack provides it
corepack enable
# Copy .env.local if it doesn't exist (contains LINEAR_API_KEY for issue creation)
cp .env.local.example .env.local # or manually source .env before running scripts
# Load environment in your shell (add to ~/.zshrc or ~/.bashrc for persistence):
source /path/to/badman/.env.local
Variables needed for scripts:
LINEAR_API_KEY— for creating Linear issues from CLI
Project Overview
Competitive badminton management platform (Badman). Backend-only Turborepo + pnpm monorepo with NestJS (backend API + workers), Sequelize ORM (PostgreSQL), Apollo GraphQL (code-first), Bull queues (Redis).
The frontend lives in a separate repository (Constitution v2.0.0, Principle V). The legacy Angular frontend was removed from this repo; do not reintroduce frontend code here.
Orchestration: Turborepo (turbo.json) over pnpm workspaces (pnpm-workspace.yaml). Deployable apps live under apps/; shared libraries are compiled internal packages under packages/, imported as @badman/<name> and resolved via workspace:* dependencies + each package's exports map (no tsconfig path aliases).
Common Commands
# Install (frozen, what CI runs)
pnpm install --frozen-lockfile
# Start Docker containers (PostgreSQL, Redis, pgAdmin)
npm run docker:up
# Serve API + sync worker in dev (watch mode; builds dependencies first)
pnpm start:server # = turbo run dev --filter=api --filter=worker-sync
# Serve the ranking workers
pnpm start:ranking
# Build everything / one project (dependencies build first via ^build)
pnpm build # = turbo run build
pnpm turbo run build --filter=api
pnpm turbo run build --filter=@badman/backend-graphql
# Run tests for a specific package
pnpm turbo run test --filter=@badman/backend-graphql
# Or run jest directly inside the package (deps must be built once first):
cd packages/backend-graphql && pnpm test
# Run only affected tests (vs a base; CI sets TURBO_SCM_BASE to the PR base)
pnpm turbo run test --affected
# Run integration tests against the dev postgres (docker-compose.dev.yml)
# Off by default; set RUN_INTEGRATION_TESTS=1 to opt in. Files named *.integration.spec.ts
# guard themselves with that env var, so a normal test run skips them.
npm run docker:up
cd packages/backend-graphql && RUN_INTEGRATION_TESTS=1 pnpm exec jest \
--testPathPattern <feature>.integration
# Lint a specific package
pnpm turbo run lint --filter=@badman/backend-graphql
# Run database migrations
npx sequelize-cli db:migrate
# Format code
prettier --write .
prettier --check .
# Seed test data
npm run seed:test-data
# Full coverage report (all packages, no DB required)
# Produces: text summary per package + lcov.info under root coverage/
pnpm test:coverage:all # = turbo run test -- --coverage
# Update coverage threshold after adding tests:
# 1. Run: pnpm test:coverage:all
# 2. Find the "Lines %" for backend-graphql in the output
# 3. Round down to nearest 5%
# 4. Edit packages/backend-graphql/jest.config.ts → coverageThreshold.global.*
# 5. Commit the updated jest.config.ts
# Cache notes: turbo caches build/test/lint per package. A no-change re-run is
# near-instant (>>> FULL TURBO). To force re-execution: append --force.
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.
- today First seen · 322 lines · 6,240 tokens per session scan A 48d15d777fd8
badman AGENTS.md is an instructions file published in the GitHub repository Badminton-Apps/badman (13 stars, last pushed today), licensed Apache-2.0. It adds 6,240 tokens to every session, about $0.0312 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-09-04.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).