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/marclove/llmc/gemini-mdgit clone --depth 1 https://github.com/marclove/llmcWrote 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/marclove/llmc/gemini-md)<a href="https://agentmods.dev/instructions/marclove/llmc/gemini-md"><img src="https://agentmods.dev/badge/instructions/marclove/llmc/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.00003 | $0.00003 |
| Opus 5 | $0.00002 | $0.00002 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00000 |
Grade A, and why
llmc 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.
This is a copy
100% identical to deepseek-harness CLAUDE.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
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.
- 3d ago First seen · 1 lines · 3 tokens per session scan A a54ff182c7e8
llmc GEMINI.md is an instructions file published in the GitHub repository marclove/llmc (10 stars, last pushed 10mo ago), licensed BSD-3-Clause. It adds 3 tokens to every session, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to deepseek-harness CLAUDE.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
git-authoring AGENTS.md
Instructions for n-shadloo/git-authoring, covering git authoring conventions, usage modes, ground rules, workflow and 1. gather context.
myace AGENTS.md
AGENTS.md instructions for niels-emmer/myace, covering myace — ai agent maintenance guidelines, what this is, commands, backend (from backend/) and frontend (from frontend/).
myace CLAUDE.md
Claude Code instructions for niels-emmer/myace, a project described as: MyACE makes your AI coding agent's rules, skills, and workflows portable.
ship-it commit.instructions.md
Instructions for khrichtchatyi/ship-it: When the user asks to commit, stage, or record changes, follow the skill in skills/commit/SKILL.md in full: operate only on the Git working tree, stage exactly the paths the user named, write one Conventional Commits message, do not push, and stop.
kaeru AGENTS.md
AGENTS.md instructions for LamantinAI/kaeru, covering agents.md — kaeru, part one — working agreements, git: commit locally in a batch, push squashed, commit authorship and pull requests.
loopgate_harness AGENTS.md
Instructions for rxdt/loopgate_harness, covering functionality, repository boundary, quality, commit and gate and documentation.