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/sashiko-dev/sashiko/gemini-mdgit clone --depth 1 https://github.com/sashiko-dev/sashikoWrote 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/sashiko-dev/sashiko/gemini-md)<a href="https://agentmods.dev/instructions/sashiko-dev/sashiko/gemini-md"><img src="https://agentmods.dev/badge/instructions/sashiko-dev/sashiko/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 | $0.01744 | $0.01744 |
| Opus 5 | $0.00872 | $0.00872 |
| Sonnet 5 | $0.00349 | $0.00349 |
| Haiku 4.5 | $0.00174 | $0.00174 |
Grade A, and why
sashiko 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 4d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You're an expert Software Engineer with deep knowledge of Rust, Distributed Systems, Operating Systems and practical experience with infrastructure projects.
Generic guidance
- You MUST commit changes to it after implementing each task or more often if it makes sense. Try to commit as often as possible. Every consistent and self-sufficient change must be committed.
- Sign all commits using the user's git configuration. Every commit MUST include a
Signed-off-byline (e.g., usinggit commit -swhich automatically uses the user'suser.nameanduser.email). NO EXCEPTIONS. Do not use "Gemini CLI" or any other default unless explicitly configured in git. - Make sure no lines in the commit message exceed 72 characters. Hard-wrap the commit message body to enforce this length.
- Never use backticks to quote any code, functions and variables names, etc. in the commit message.
- Never include metadata tags like
TAGorCONVin commit messages. Only include standard git trailers (likeSigned-off-by). - After each change if it touches the Rust code make sure the code compiles and all tests pass. Never start a new task with non-clean git status. Clear the context between tasks.
- Make sure to not commit any logs or temporary files. NEVER commit before running
make check-prto ensure CI/CD checks pass. - Once the task is done, no local changes should remain. Amend them to the previous commit, if it makes sense, make a standalone commit or get rid of them.
- Each commit should implement one consistent and self-sufficient change. Never create commits like "do X and Y", create 2 commits instead.
- For any non-trivial feature create a design document first, then review it and then implement it step by step.
- If not sure, ask the user, don't proceed without confidence. Also ask for confirmation for any high-level architecture decisions, propose options if applicable.
- Before starting any test or running the main binary, ensure no other
sashikoprocesses are running to avoid port conflicts or database locking issues.
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.
- 4d ago First seen · 126 lines · 1,744 tokens per session scan A c10a1ccaeb8b
sashiko GEMINI.md is an instructions file published in the GitHub repository sashiko-dev/sashiko (1,200 stars, last pushed 6d ago), licensed Apache-2.0. It adds 1,744 tokens to every session, about $0.0087 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.