Borrowing it
Nothing to install: this file belongs to bobbylough/ai-pit-crew. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bobbylough/ai-pit-crew/main/GEMINI.mdgit clone --depth 1 https://github.com/bobbylough/ai-pit-crewWrote 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/bobbylough/ai-pit-crew/gemini-md)<a href="https://agentmods.dev/instructions/bobbylough/ai-pit-crew/gemini-md"><img src="https://agentmods.dev/badge/instructions/bobbylough/ai-pit-crew/gemini-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/bobbylough/ai-pit-crew/gemini-md"><img src="https://agentmods.dev/badge/instructions/bobbylough/ai-pit-crew/gemini-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00552 | $0.00552 |
| Opus 5 | $0.00276 | $0.00276 |
| Sonnet 5 | $0.00110 | $0.00110 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
ai-pit-crew GEMINI.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 8d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gemini Code Assist Instructions
You are a contributor on this project. Read AGENTS.md for the full agent contract.
Engineering Principles
Produce maintainable, reliable, secure, production-ready code. Prefer the simplest solution that fully satisfies the requirements. Follow KISS and YAGNI. Optimize for readability and maintainability over cleverness.
Code Standards
- Use clear, descriptive names — good naming eliminates the need for most comments
- Keep functions focused on a single responsibility
- Follow existing project patterns unless there is a compelling reason to improve them
- Remove dead code and unused variables
Commenting Guidelines
Write code that speaks for itself. Comment only when necessary to explain why, not what.
Do not write:
- Comments that restate what the code clearly does
- Redundant comments duplicating functionality
- Changelog entries or decorative dividers
Do write comments for:
- Complex business logic requiring context
- Non-obvious algorithm choices
- External API constraints or limitations
- Workarounds for specific known bugs or platform issues
Security Requirements
Apply OWASP Top 10 guidelines to all code.
- Use parameterized queries — never concatenate user input into SQL
- Sanitize and escape all output rendered to HTML
- Never store plaintext passwords — use bcrypt, scrypt, or Argon2
- Validate JWTs server-side on every protected request
- Enforce authorization checks on the server — never rely on client-side checks
- Never hardcode secrets, API keys, or credentials in source code
- Validate and sanitize all external input at system boundaries
- Do not introduce packages with known critical vulnerabilities
Code Review Approach
When reviewing code, use this priority structure:
Critical — fix before merge:
- Security vulnerabilities (injection, exposed secrets, missing auth checks)
- Correctness bugs and broken logic
- Data loss risk
Important — address in this PR:
- Missing tests for new behavior
- Performance issues (N+1 queries, unbounded loops)
- Architecture inconsistency with
docs/architecture.md - Error handling gaps
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.
- 8d ago First seen · 74 lines · 552 tokens per session scan A 4d9acb0b540f
ai-pit-crew GEMINI.md is an instructions file published in the GitHub repository bobbylough/ai-pit-crew (2 stars, last pushed 3mo ago), licensed MIT. It adds 552 tokens to every session, about $0.0028 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
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).
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).
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.
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.