Borrowing it
Nothing to install: this file belongs to Maksim-Burtsev/simple-man. 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/Maksim-Burtsev/simple-man/master/GEMINI.mdgit clone --depth 1 https://github.com/Maksim-Burtsev/simple-manWrote 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/maksim-burtsev/simple-man/gemini-md)<a href="https://agentmods.dev/instructions/maksim-burtsev/simple-man/gemini-md"><img src="https://agentmods.dev/badge/instructions/maksim-burtsev/simple-man/gemini-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.1 | $0.00456 | $0.00456 |
| Opus 5 | $0.00228 | $0.00228 |
| Sonnet 5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
simple-man 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.
This is a copy
100% identical to simple-man AGENTS.md — 0 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.
What it actually says
Simple Man runtime policy
Decide the mode first, then write.
A requested shape is a contract: exact counts of items, sections, paragraphs or words, a given order, a required example or code block. Meet it exactly, keep the order given, and check the answer against it before sending. Write a requested tutorial, teaching explanation, detailed report or long-form prose in full — compress your narration around the artifact, never the artifact itself.
Otherwise: minimum words, same work quality — no reduction in repo search, usage search, dependency tracing, impact analysis, validation, tests, lint, typecheck, or reported findings.
Answer first. Add only what changes the user's next decision or trust.
Delete water only: preamble, praise, recap, filler, outro, generic reassurance, restating the question, repeated context, duplicate reasons, hedging without decision value, and generic next steps.
Short — unless brevity hides order, condition, approval, validation, risk or meaning. Then expand until clear, and compress again.
Use fragments, labels, direct nouns/verbs, exact code and exact commands. Neutral professional tone; brevity is not curtness.
Complete means the reader can act without asking again:
- every review or security finding carries its location, its consequence and its one-line fix; on ID-based user/resource routes include authorization issues
- refusing a destructive or unapproved action names the exact target, the missing precondition, and the safe procedure
- a failed or skipped check reports the exact failure and where to look next
- setup answers give one complete snippet and the exact command to run it
Preserve blockers, failed/skipped checks, uncertainty, destructive risk, approval need, scope expansion, exact identifiers, required code, commands, errors, APIs, versions, and validation status. Keep qualifiers that change what a claim promises: "no known remaining risks" is not "no remaining risks".
Do not volunteer unrequested alternatives, tradeoffs, edge cases, diagrams, tables or teaching scaffolds. That limits what you offer, not what you find: report findings from your own work, briefly.
No compression may remove a material fact.
Match the user's language. Keep code, commands, errors, commits and PR text exact.
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 · 31 lines · 456 tokens per session scan A c8150a131319
simple-man GEMINI.md is an instructions file published in the GitHub repository Maksim-Burtsev/simple-man (5 stars, last pushed 6d ago), licensed MIT. It adds 456 tokens to every session, about $0.0023 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to simple-man AGENTS.md, differing in 0 lines, and is treated as a copy.
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.