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/quantmind/quantflow/makefilegit clone --depth 1 https://github.com/quantmind/quantflowWhat 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.00092 | $0.00092 |
| Opus 5 | $0.00046 | $0.00046 |
| Sonnet 5 | $0.00018 | $0.00018 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
quantflow makefile.instructions.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 yesterday.
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
Makefile Conventions
- Keep all targets sorted alphabetically.
helptarget is the exception and should be the first target in the file.- targets should be separated by a one blank line only.
- Each target should have a one-line description, starting with
##, that describes what the target does. This description is used by thehelptarget to generate documentation for all targets.
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.
- yesterday First seen · 11 lines · 92 tokens per session scan A 7515c0e5a8cc
quantflow makefile.instructions.md is an instructions file published in the GitHub repository quantmind/quantflow (52 stars, last pushed 15d ago), licensed BSD-3-Clause. It adds 92 tokens to every session, about $0.0005 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
maverick-mcp AGENTS.md
Instructions for wshobson/maverick-mcp, covering repository guidelines, project overview, project structure, documentation map and build, test, and development commands.
awesome-quant AGENTS.md
AGENTS.md instructions for wilsonfreitas/awesome-quant, covering agents.md, project overview, architecture, commands and install deps (requires python 3.11+).
TradingAgents-Telegram CLAUDE.md
Instructions for IvanWng97/TradingAgents-Telegram, covering tradingagents-telegram — architecture reference, layout, architecture (for code reviewers), request lifecycle (manual /watch tap) and state ownership.
tiingo-mcp AGENTS.md
Instructions for major7apps/tiingo-mcp, covering agents.md, project map, public contract, operating rules and commands.
deckforge CLAUDE.md
Instructions for Whatsonyourmind/deckforge, covering deckforge, tech stack, project structure, key commands and local development.
open-stocks-mcp CLAUDE.md
Instructions for Open-Agent-Tools/open-stocks-mcp, covering claude.md, project overview, quick reference, development setup and testing.