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/sergeiwallace/ai-cli-utils/gemini-mdgit clone --depth 1 https://github.com/sergeiwallace/ai-cli-utilsWrote 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/sergeiwallace/ai-cli-utils/gemini-md)<a href="https://agentmods.dev/instructions/sergeiwallace/ai-cli-utils/gemini-md"><img src="https://agentmods.dev/badge/instructions/sergeiwallace/ai-cli-utils/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.01013 | $0.01013 |
| Opus 5 | $0.00507 | $0.00507 |
| Sonnet 5 | $0.00203 | $0.00203 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
ai-cli-utils 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 3d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ai-cli-utils — Gemini Context
You are invoked as a research and review partner. Your primary tasks are parallel research and code review alongside Claude Code. You do not implement features directly.
Tech Stack
| Layer | Technology |
|---|---|
| Core | Python |
| AI orchestration | Claude Code CLI + Gemini CLI |
Development Conventions
-
Scope control: Implement only what the spec requires
-
Test naming:
test_{given}_{when}_{then}/it("should {action} when {condition}") -
Commits: Atomic
-
Commit at working checkpoints — commit and push to your feature branch at each working checkpoint (feature functional, doc ready, task added, etc.). Don't leave uncommitted changes at end of session.
-
Dev branch:
main— feature branches merged via PR
Public Open-Source Package Standards
This is a public open-source package. All code, docs, comments, tests, and commit messages must be written for a general audience.
- No proprietary names — never reference ai-core, aido, or any private platform/tool names in code, docs, comments, or tests
- No personal identifiers — no personal names (first or last), usernames, private server IPs/hostnames, or account-specific paths. Use generic placeholders:
user,myproject,example.com,192.0.2.x - No private project names or prefixes — don't hardcode any project names or session prefixes from personal workflow in source, docs, or tests. Use only fully generic names:
myproject,myapp,session-1,test-session - Generic examples throughout — all session names, project names, and config values in tests/docs must be obviously placeholder. Nothing that could be mistaken for a real personal workflow artifact.
- OS portability — all code must account for Windows, macOS, and Linux differences. No macOS-only assumptions (e.g.
~/Library/,pbcopy,open). Usesys.platform,pathlib, andosabstractions. Flag any unavoidably platform-specific code with a comment. - Commit messages are public — same rules apply to git commit messages
- If you catch an existing violation while working, flag it immediately rather than letting it accumulate
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.
- 3d ago First seen · 71 lines · 1,013 tokens per session scan A b63b3a1a913a
ai-cli-utils GEMINI.md is an instructions file published in the GitHub repository sergeiwallace/ai-cli-utils (2 stars, last pushed 3d ago), licensed MIT. It adds 1,013 tokens to every session, about $0.0051 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
ai-workflow AGENTS.md
Instructions for cunhaax/ai-workflow, covering ai workflow template, rules — non-negotiable, project overview, commands and architecture.
trackly-cli CLAUDE.md
Claude Code instructions for trackly-app/trackly-cli, covering trackly-cli, tech stack, backend production source of truth, directory structure and key commands.
vibetags com-example-config-AsyncTestConfig.instructions.md
Instructions for PIsberg/vibetags, covering copilot instructions for asynctestconfig and immutable type.
pupila CLAUDE.md
Instructions for FranRom/pupila, covering claude.md, where things live, stack, run locally and repo layout.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
McpServer AGENTS.md
AGENTS.md instructions for sharpninja/McpServer, covering agent instructions, session start, rules, byrd test gate and where things live.