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 rules/feral-file/ff-cli/01-master-contractgit clone --depth 1 https://github.com/feral-file/ff-cliWhat 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.00443 | $0.00443 |
| Opus 5 | $0.00221 | $0.00221 |
| Sonnet 5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
01-master-contract 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 2d 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.
What it actually says
FF1-CLI Master Contract
Use this rule as the top-level working contract for this repository.
Repository scope
- Node.js CLI for FF1 computational art workflows and DP-1 playlist operations.
- Keep terminology precise:
FF1,DP-1 envelope,DP-1 conformance,computational art playlist,channel endorsement,FF1 device.
Non-negotiables
- Prefer replacing or deleting flawed code paths over narrow local fixes when that yields a clearer design.
- Do not preserve legacy behavior, compatibility shims, migrations, or transitional paths unless explicitly requested.
- Keep functions small, composable, and testable.
- Prefer comments that preserve durable context for future agent sessions.
- When logic is non-obvious, document design intent, trade-offs, invariants, external dependencies, and coding constraints near the code.
- Update JSDoc for new and changed functions.
- Use TypeScript for new or updated source when practical.
Comment style
- Follow a Go-style documentation posture.
- Write comments as full sentences.
- Start symbol doc comments with the symbol name.
- Prefer comments that explain
whyand constraints over comments that narrate syntax. - Add comments freely when they help a later agent amend the code safely.
Repo-specific constraints
- Only these docs may be edited:
docs/README.md,docs/FUNCTION_CALLING.md,docs/EXAMPLES.md,docs/CONFIGURATION.md,docs/RELEASING.md,docs/PROJECT_SPEC.md. - Do not add new process docs under
/docsor the repo root. - Only update docs when behavior changes.
- Config priority is
config.json>.env> defaults. - Temporary debug scripts belong in
/.tmpand should not be committed.
Reserved owner-owned policy
- Architecture boundaries:
TBD by repo owner - API design rules:
TBD by repo owner
Do not invent permanent architecture or API policies beyond small, local improvements until the owner fills these sections in.
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.
- 2d ago First seen · 42 lines · 443 tokens per session scan A 90afdd96f730
01-master-contract is a cursor rule published in the GitHub repository feral-file/ff-cli (5 stars, last pushed 14d ago), licensed MIT. It adds 443 tokens to every session, about $0.0022 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.