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/victusfate/scaffold/gemini-mdgit clone --depth 1 https://github.com/victusfate/scaffoldWrote 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/victusfate/scaffold/gemini-md)<a href="https://agentmods.dev/instructions/victusfate/scaffold/gemini-md"><img src="https://agentmods.dev/badge/instructions/victusfate/scaffold/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.00012 | $0.00012 |
| Opus 5 | $0.00006 | $0.00006 |
| Sonnet 5 | $0.00002 | $0.00002 |
| Haiku 4.5 | $0.00001 | $0.00001 |
Grade A, and why
scaffold 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
Follow all guidelines in AGENTS.md at the project root.
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 · 2 lines · 12 tokens per session scan A 54fa62a0df2f
scaffold GEMINI.md is an instructions file published in the GitHub repository victusfate/scaffold (6 stars, last pushed today), licensed MIT. It adds 12 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
lastlight CLAUDE.md
Instructions for nearform/lastlight, covering last light — monorepo orientation, workspace map, published packages (seven), dependency graph (workspace edges) and logging — use the logger, never console.
momo-code AGENTS.md
AGENTS.md instructions for momozi1996/momo-code, covering agents.md -- project agent instructions, how to work with this codebase, getting started, making changes and quality gates (enforced).
momo-code CLAUDE.md
Claude Code instructions for momozi1996/momo-code, covering claude.md -- agent working agreement, project context, code patterns, testing and commit style.
specship CLAUDE.md
Instructions for bonnguyenitc/specship, covering specship — dev guide, verify every change and learnings.
specship copilot-instructions.md
Instructions for bonnguyenitc/specship: For any non-trivial change, follow .specship/skills/WORKFLOW.md and the per-stage playbooks in .specship/skills/ss- /SKILL.md.
costrict AGENTS.md
Instructions for zgsm-ai/costrict: This file provides guidance to agents when working with code in this repository.