Borrowing it
Nothing to install: this file belongs to fmind/agent-levers. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fmind/agent-levers/main/AGENTS.mdgit clone --depth 1 https://github.com/fmind/agent-leversWrote 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/fmind/agent-levers/agents-md)<a href="https://agentmods.dev/instructions/fmind/agent-levers/agents-md"><img src="https://agentmods.dev/badge/instructions/fmind/agent-levers/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/fmind/agent-levers/agents-md"><img src="https://agentmods.dev/badge/instructions/fmind/agent-levers/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.00630 | $0.00630 |
| Opus 5.5 | $0.00252 | $0.00252 |
| Sonnet 5.5 | $0.00126 | $0.00126 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
agent-levers AGENTS.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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Overview
- agent-levers ships a small set of slash-command skills (
/lever-init,/lever-new,/lever,/lever-status) that give a coding agent a structured plan → do → check → act loop. - Skills are file-based and harness-agnostic: the same
skills/tree works in Claude Code, Gemini CLI, GitHub Copilot, and OpenCode. - Repo state is
.agents/levers/<id>-<slug>/{lever.yaml, LEVER.md}—lever.yamlvalidated againstlever.schema.json.
Conventions
-
Line caps. Skill files exist to be loaded by an agent on every run; verbosity directly costs context budget. Targets:
SKILL.md— ≤ 110 linesskills/lever/references/*.md— ≤ 100 lines (each step procedure)skills/lever/templates/*.md— ≤ 50 lines (each LEVER.md section template)skills/*/templates/*.md— ≤ 50 lines (other artifact templates)- Project-root markdown (
README.md,AGENTS.md) — uncapped, but tighten when it sprawls
When a file approaches its cap, prefer cutting motivational/explanatory prose over removing structural rules. Each rule should be stated once, in the imperative, in the file the agent loads when it needs it. The "why" lives in commit messages and PR descriptions.
-
Lint. Run
npm run lintandnpm run validateto validate changes —lintcovers Prettier formatting and markdownlint-cli2;validateruns ajv against everyexamples/**/lever.yaml. Both gatepre-commitlocally and CI. -
Voice. Skill bodies address the agent in the imperative ("Read X, then write Y"). Avoid second-person flavor text aimed at the human reader — that belongs in the README.
Workflow
- Use lever skills (this repo dogfoods its own framework on non-trivial changes):
/lever-new <title>— capture a new task (Session 1: discuss intent, write the brief)/lever <id>— run the chain (Session 2: plan → do → check → act → done, autonomously until paused or finished)/lever-status— inspect levers in flight;/lever-status <id> cancel [<reason>]— retire one
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.
- 1mo ago First seen · 37 lines · 630 tokens per session scan A cfb1cec22be3
agent-levers AGENTS.md is an instructions file published in the GitHub repository fmind/agent-levers (3 stars, last pushed 3d ago), licensed MIT. It adds 630 tokens to every session, about $0.0025 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.