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/oakninja/makeme/gemini-mdgit clone --depth 1 https://github.com/OakNinja/MakeMeWrote 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/oakninja/makeme/gemini-md)<a href="https://agentmods.dev/instructions/oakninja/makeme/gemini-md"><img src="https://agentmods.dev/badge/instructions/oakninja/makeme/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.00390 | $0.00390 |
| Opus 5 | $0.00195 | $0.00195 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
MakeMe 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 today.
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
Project Overview
MakeMe is a command-line tool written in Go that helps you interactively select and run make targets from a Makefile. It is a cross-platform replacement for the original MakeMeFish script.
Building and Running
- Build: To build the executable, run the following command:
go build ./cmd/makeme - Run: To run the application, execute the following command in a directory containing a Makefile:
./makeme
Installation
Via Script
To install MakeMe and the optional shell integration, run the following command:
./install.sh
Via Homebrew (macOS and Linux)
To install MakeMe via Homebrew, use the custom tap:
brew tap OakNinja/tap
brew install mm
To install the latest development version:
brew install OakNinja/tap/mm --HEAD
Shell Integration
The install.sh script will offer to install shell integration for you. This will add a shell function mm that, when used, will place the selected make command directly into your command line, ready for you to execute.
After running the script, you will need to restart your shell or source the configuration file to apply the changes, for example:
source ~/.bashrc
Usage
Once installed, you can use the mm command:
mm
After you select a target, the make command will appear in your prompt.
Development Conventions
- Project Structure: The project follows the standard Go project structure.
- Testing: Tests are located in the
internal/makemedirectory and can be run with the following command:go test ./...
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.
- today First seen · 67 lines · 390 tokens per session scan A 55ec7ffcdfa6
MakeMe GEMINI.md is an instructions file published in the GitHub repository OakNinja/MakeMe (8 stars, last pushed 8mo ago), licensed MIT. It adds 390 tokens to every session, about $0.0019 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-09-04.
Other instructions, from other repositories
chatgpt-cli AGENTS.md
AGENTS.md instructions for kardolus/chatgpt-cli, covering agents.md, 1) repo map (where things usually live), 2) build & test workflow (use makefile first), 3) go version and 4) testing expectations (required).
dingtalk-workspace-cli AGENTS.md
AGENTS.md instructions for DingTalk-Real-AI/dingtalk-workspace-cli, covering repository agent guide, build and test, command framework declaration, flag / help / schema homology and agent schema contract.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.
unraid-management-agent copilot-instructions.md
Copilot instructions for ruaan-deysel/unraid-management-agent, covering copilot instructions, copilot workflow, path-specific instructions, reusable prompts and quick commands.
coral CLAUDE.md
Instructions for cdknorow/coral, covering claude.md - coral go, mission, testing, go unit tests and legacy parity tools (historical reference).
oastools GEMINI.md
Instructions for erraggy/oastools, covering gemini.md, project overview, building and running, key commands and development conventions.