Borrowing it
Nothing to install: this file belongs to zgbrenner/agentcounsel. 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/zgbrenner/agentcounsel/main/GEMINI.mdgit clone --depth 1 https://github.com/zgbrenner/agentcounselWrote 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/zgbrenner/agentcounsel/gemini-md)<a href="https://agentmods.dev/instructions/zgbrenner/agentcounsel/gemini-md"><img src="https://agentmods.dev/badge/instructions/zgbrenner/agentcounsel/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.00482 | $0.00482 |
| Opus 5 | $0.00241 | $0.00241 |
| Sonnet 5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
agentcounsel 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 6d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentCounsel — Gemini CLI Context
You are working with AgentCounsel, an open, Markdown-native legal skills library. This file is the Gemini CLI extension context for the library: it tells a Gemini agent how to operate here.
AgentCounsel is a collection of standalone legal skills. Each skill is a structured workflow that produces draft legal work product for attorney review — never a final answer, never an opinion. The skills supply discipline and structure; a qualified, licensed legal professional must review and adopt every output. AgentCounsel is not a law firm and does not provide legal advice.
Non-negotiable operating model
- Produce draft legal work product for attorney review only. Attorney review is always required.
- Never invent legal authority, citations, quotations, facts, or deadlines.
- AgentCounsel is jurisdiction-agnostic: skills carry workflow discipline, not the law. Flag jurisdiction-specific points for verification instead of stating a statute, case, rule, or doctrine as authority.
- Preserve confidentiality and privilege. Keep client-sensitive facts out of templates.
- Flag every gap with a visible placeholder (
[CONFIRM: ...],[VERIFY: ...]) rather than guessing.
How to work in this repository
- Read every file in
core/first — the seven operating rules every skill inherits. They always apply. - Route the task with
WORKFLOW_ROUTER.md; browse withSKILLS_INDEX.md. - Open the single narrowest relevant skill: its
SKILL.mdand any file in itstemplates/folder. Do not load unrelated practice areas. - Follow the skill's Required Inputs gate, Workflow, and Output Format exactly.
- Hand off with the skill's Attorney Verification Checklist completed.
If no skill fits the task, say so. Do not improvise a legal workflow.
CONTEXT.md defines the repository's vocabulary — read it to use terms like
"skill," "template," and "canonical" precisely.
The full operating guide and the Gemini CLI tool reference are imported below.
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.
- 6d ago First seen · 45 lines · 482 tokens per session scan A 52b0ce7ea306
agentcounsel GEMINI.md is an instructions file published in the GitHub repository zgbrenner/agentcounsel (18 stars, last pushed 1mo ago), licensed MIT. It adds 482 tokens to every session, about $0.0024 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
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.