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/akasecurity/claude-tools/gemini-mdgit clone --depth 1 https://github.com/akasecurity/claude-toolsWrote 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/akasecurity/claude-tools/gemini-md)<a href="https://agentmods.dev/instructions/akasecurity/claude-tools/gemini-md"><img src="https://agentmods.dev/badge/instructions/akasecurity/claude-tools/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.00017 | $0.00017 |
| Opus 5 | $0.00009 | $0.00009 |
| Sonnet 5 | $0.00003 | $0.00003 |
| Haiku 4.5 | $0.00002 | $0.00002 |
Grade A, and why
claude-tools 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.
What it actually says
GEMINI.md — aka-claude-tools
@./AGENTS.md
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 · 4 lines · 17 tokens per session scan A 3a443c4d25ac
claude-tools GEMINI.md is an instructions file published in the GitHub repository akasecurity/claude-tools (10 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session, about $0.0001 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
stride-gpt AGENTS.md
AGENTS.md instructions for mrwadams/stride-gpt, covering agents.md, what this project is, repository layout, how the agentic analysis works and progressive disclosure pattern.
.context copilot-instructions.md
Copilot instructions for forefy/.context: This repo contains instruction files for using and conducting security reviews, do not confuse this copilot-instructions.md from other copilot-instructions files existing in this workspace.
assay CLAUDE.md
Claude Code instructions for Rul1an/assay, covering assay - ai agent context, what is assay?, workspace structure, key commands and cli entry points.
tengu CLAUDE.md
Instructions for rfunix/tengu, covering claude.md — tengu mcp server, project overview, architecture, request flow and module map.
claude-skills CLAUDE.md
Instructions for mastepanoski/claude-skills, covering claude.md, repository purpose, testing skills locally, repository architecture and core structure.
guardvibe CLAUDE.md
Instructions for goklab/guardvibe, covering project guidelines, guardvibe security scanner, when user asks for security scan/fix, never do these and quick reference.