Borrowing it
Nothing to install: this file belongs to mrinalwadhwa/fluent. 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/mrinalwadhwa/fluent/main/AGENTS.mdgit clone --depth 1 https://github.com/mrinalwadhwa/fluentWrote 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/mrinalwadhwa/fluent/agents-md)<a href="https://agentmods.dev/instructions/mrinalwadhwa/fluent/agents-md"><img src="https://agentmods.dev/badge/instructions/mrinalwadhwa/fluent/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/mrinalwadhwa/fluent/agents-md"><img src="https://agentmods.dev/badge/instructions/mrinalwadhwa/fluent/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.01408 | $0.01408 |
| Opus 5.5 | $0.00563 | $0.00563 |
| Sonnet 5.5 | $0.00282 | $0.00282 |
| Haiku 4.5 | $0.00141 | $0.00141 |
Grade A, and why
fluent 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions for Coding Agents
These instructions define how Coding Agents should assist with this project.
Fluent workflow
Use the fluent to build the fluent. For non-trivial code,
documentation, skill, expertise, or behavior changes, follow the
fluent skill and go through the Fluent lifecycle:
brief, behaviors, approach, plan, execution, review, and land.
Do not implement substantial product/code changes directly on main.
Use Fluent Work Items and Attempts for delegated build work that needs
isolation, reviewers, and merging. The Work model path is: Work Item,
Attempt, Task, Workspace, and Merge Candidate.
Conversation agents may edit Fluent planning and memory state directly when they are collaborating with the user in the discussion loop: observations, briefs, behavior drafts, approaches, plans, lightweight curation, and similar durable notes. These edits are part of shaping work, not delegated execution.
Do not meddle with live execution state directly: branches, worktrees, statuses, session artifacts, and merging state belong to the execution system. Modify them only during explicit recovery with the user.
Keep main available as a stable integration branch for Work to rebase
from and merge into. If conversation-state edits could overlap with
active Work or merging, make them on a lightweight discussion branch
or worktree and land them separately instead of dirtying main.
Use fluent observations add to record future work and lessons.
Open observations live as one file per entry under
.fluent/observations/; resolved ones move to
.fluent/observations/resolved/. Inspect with fluent observations list and fluent observations show <id>.
Commit messages
Subject line
- Use imperative mood and active voice
- Start with a verb: "Add", "Fix", "Update", "Remove", "Refactor"
- Keep under 50 characters
- Capitalize the first letter
- Do not end with a period
- Describe the change, not the process that led to it
- Good: "Fix sandbox worktree binding"
- Bad: "Run review and fix issues found"
- Bad: "Address reviewer findings"
- Use "Improve" over "Fix" when the change enhances something that was working but could be better. "Fix" implies it was broken.
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 Changed · +16 lines · +161 tokens per session 5696343336c3
- 1mo ago First seen · 157 lines · 1,247 tokens per session scan A 67f2ac57e82c
fluent AGENTS.md is an instructions file published in the GitHub repository mrinalwadhwa/fluent (121 stars, last pushed 9d ago), licensed Apache-2.0. It adds 1,408 tokens to every session, about $0.0056 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-30.
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).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.