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/structuregit 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/structure)<a href="https://agentmods.dev/instructions/badminton-apps/badman/structure"><img src="https://agentmods.dev/badge/instructions/badminton-apps/badman/structure.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.00951 | $0.00951 |
| Opus 5 | $0.00476 | $0.00476 |
| Sonnet 5 | $0.00190 | $0.00190 |
| Haiku 4.5 | $0.00095 | $0.00095 |
Grade A, and why
badman structure.instructions.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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions for Badman Project
Project Overview
Badman is a comprehensive badminton management system built with Angular 19, Node.js, and TypeScript using Nx monorepo architecture. The application handles player management, tournament organization, ranking systems, and club administration.
Architecture & Technologies
- Monorepo: Nx workspace with advanced dependency management
- Frontend: Angular 19 with Material Design, PWA capabilities
- Backend: Node.js with GraphQL API
- Database: PostgreSQL with Sequelize ORM
- Cache: Redis
- Testing: Jest (unit), Playwright (E2E)
- Build Tools: Webpack, Angular CLI
Key Directory Structure
Applications (apps/)
apps/badman/- Main Angular frontend (serves at localhost:3000)apps/api/- GraphQL API server and business logicapps/worker/- Background workers for sync, ranking, and regional processingapps/scripts/- Development and deployment scriptsapps/*-e2e/- End-to-end test suites (desktop, mobile, shared base)
Libraries (libs/)
Backend Libraries (libs/backend/):
- Core:
authorization/,database/,graphql/,cache/,queue/ - Business:
competition/,ranking/,notifications/,mailing/ - Integrations:
twizzit/,belgium/flanders/ - Utils:
search/,translate/,visual/,validation/,websockets/
Frontend Libraries (libs/frontend/):
- Core:
models/,graphql/,auth/,components/,utils/ - Pages:
club/,player/,team/,ranking/,tournament/,competition/ - Services:
seo/,translation/,pdf/,excel/,notifications/,queue/
Shared: libs/utils/ - Cross-platform utilities
Other Important Directories
database/- Migrations, config, scriptsmails/- HTML email templatesscripts/- Build and deployment scriptstypes/- Global TypeScript definitions
Development Guidelines
File Creation Patterns
- Angular Components: Place in appropriate feature library under
libs/frontend/ - Backend Services: Place in relevant domain library under
libs/backend/ - Shared Models: Use
libs/frontend/models/orlibs/utils/ - GraphQL: Schema in
libs/backend/graphql/, queries inlibs/frontend/graphql/ - Tests: Co-locate with source files or in
apps/*-e2e/for E2E tests
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 · 104 lines · 951 tokens per session scan A 0c324c2dd643
badman structure.instructions.md is an instructions file published in the GitHub repository Badminton-Apps/badman (13 stars, last pushed today), licensed Apache-2.0. It adds 951 tokens to every session, about $0.0048 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).