Borrowing it
Nothing to install: this file belongs to feral-file/ff-cli. 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/feral-file/ff-cli/main/AGENTS.mdgit clone --depth 1 https://github.com/feral-file/ff-cliWrote 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/feral-file/ff-cli/agents-md)<a href="https://agentmods.dev/instructions/feral-file/ff-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/feral-file/ff-cli/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/feral-file/ff-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/feral-file/ff-cli/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.01659 | $0.01659 |
| Opus 5.5 | $0.00664 | $0.00664 |
| Sonnet 5.5 | $0.00332 | $0.00332 |
| Haiku 4.5 | $0.00166 | $0.00166 |
Grade A, and why
ff-cli 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 2mo 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — ff-cli Repository Contract
This file is the repository-level contract for humans and coding agents working in ff-cli.
It defines how work is done in this repo. Tool-specific details live in .cursor/, opencode.json, and shared review prompts.
Repository overview
- Project:
ff-cli - Purpose: a Node.js CLI for FF1 computational art workflows, DP-1 envelopes, playlist validation, playlist publishing, and FF1 device operations
- Primary runtime: Node.js + TypeScript
- Domain terms to keep consistent:
FF1,DP-1 envelope,DP-1 conformance,computational art playlist,channel endorsement,FF1 device
Portable operating model
Default sequence:
spec -> design -> tasks -> tests -> implementation -> verification -> review -> merge
TDD is the default discipline for behavior changes. For small, low-risk fixes, the sequence can be compressed, but work must still remain scoped, verified, reviewed, and traceable.
Non-negotiables
- Prefer replacing or deleting flawed code paths over narrow local patches when that yields a clearer design.
- Do not preserve legacy behavior, compatibility shims, migrations, or transitional paths unless explicitly requested.
- Keep functions small, single-purpose, and testable. Break up functions that exceed roughly 30 lines, carry multiple concerns, or hide business rules in branching.
- Use TypeScript for new or updated source when practical. Legacy
.jsfiles may remain until intentionally migrated. - Prefer comments that carry durable engineering context for future amendment by later agent sessions.
- When code is non-obvious, store design intent, trade-offs, invariants, edge cases, and coding constraints in comments near the code they govern.
- Update JSDoc whenever a function changes. New or updated functions should have complete JSDoc.
Coding style and comments
- Follow a Go-style documentation standard for comments even though the repo is TypeScript-first.
- Write comments as clear sentences. Start doc comments with the symbol name when documenting a function, type, constant, or module.
- Prefer comments that explain
why,why now,why this shape, andwhat must not changeover comments that restate syntax. - Add comments generously when the code encodes business rules, validation invariants, protocol expectations, fallback behavior, security assumptions, or trade-offs that would be easy for a later agent to break.
- Keep short obvious code paths uncommented. Extra comments are encouraged only when they add future maintenance value.
- When a compromise is intentional, record the constraint and rejected alternative in the comment.
- When behavior depends on external systems or repo conventions, record that dependency in the comment so a later agent can amend safely.
- Preserve high-signal comments during refactors. Update them when the reasoning changes.
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.
- 2mo ago First seen · 140 lines · 1,659 tokens per session scan A 7ac7093d8367
ff-cli AGENTS.md is an instructions file published in the GitHub repository feral-file/ff-cli (5 stars, last pushed today), licensed MIT. It adds 1,659 tokens to every session, about $0.0066 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).
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.