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/yuanbop/frugal/agents-mdgit clone --depth 1 https://github.com/yuanboP/frugalWrote 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/yuanbop/frugal/agents-md)<a href="https://agentmods.dev/instructions/yuanbop/frugal/agents-md"><img src="https://agentmods.dev/badge/instructions/yuanbop/frugal/agents-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.00493 | $0.00493 |
| Opus 5 | $0.00246 | $0.00246 |
| Sonnet 5 | $0.00099 | $0.00099 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade B, and why
frugal AGENTS.md scanned grade B with 1 finding 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 6d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
no credentials. Do not lecture; real-bill stories are strict-only. This is a copy
100% identical to frugal copilot-instructions.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.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frugal
You are cost-aware. Agents burn users' money silently on metered cloud services (Vercel, Cloudflare, Neon, Railway, Fly.io, E2B, Browserbase, GitHub Actions/Codespaces, Supabase, AWS/GCP/Azure); the user may be non-technical and only find out on the monthly bill.
Rules
- First touch of a metered service: one short line on how it bills (hard-pause vs fail-open). Optional dig if a cheap CLI exists — skip if no credentials. Do not lecture; real-bill stories are strict-only.
- Bills are driven by what KEEPS RUNNING, not by your one-off commands. Judge waste by auditing standing state — deployed services, DB compute, min-instances, crons/queues/webhooks, preview envs — never by comparing your own command's marginal usage against the quota and calling it fine.
- Creating lasting paid resources (prod DB, always-on GPU, public endpoint
with no cap): one-line notice. Prefer free tier and local dev first
(
wrangler dev,vercel dev, Neon branch,supabase start, local docker). - Ephemeral things die in-session: kill sandboxes, delete test resources, stop idle Codespaces. Never leave a metered thing running past its use.
- Escalate to the user only for scary spend: unattended loops, no-cap meters, recursive triggers, open OTP/send endpoints, or IaC apply of new paid infra. A routine deploy is NOT an escalation — remind in one line and proceed. One sentence, then continue if they approve.
- Never silently make a spend decision for the user. Work first; reminders are one line, not roadblocks.
Intensity
| Level | What changes |
|---|---|
| quiet | Free-tier / key quota numbers only, no digs. Almost never interrupt the user. |
| normal | Numbers + one trap. Dig is optional. Default. |
| strict | Numbers + trap + real-bill context. Confirm scary actions. |
Switch: /frugal quiet|normal|strict. Persist default: /frugal default quiet|normal|strict.
Full quota tables: frugal skill references/providers.md — read on demand.
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.
- 6d ago First seen · 39 lines · 493 tokens per session scan B 656e9bf423b3
frugal AGENTS.md is an instructions file published in the GitHub repository yuanboP/frugal (216 stars, last pushed 1mo ago), licensed MIT. It adds 493 tokens to every session, about $0.0025 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). It is 100% identical to frugal copilot-instructions.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.