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/complynx/ff-mcp/agents-mdgit clone --depth 1 https://github.com/complynx/ff-mcpWrote 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/complynx/ff-mcp/agents-md)<a href="https://agentmods.dev/instructions/complynx/ff-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/complynx/ff-mcp/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 | $0.00544 | $0.00544 |
| Opus 5 | $0.00272 | $0.00272 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
ff-mcp 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 3d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent rules
Goal: set up local ff-mcp from repo. Full runbook: docs/agent-setup.md. User guide: docs/user-setup.md.
Hard limits
- Need explicit user profile choice. Never guess profile.
- Ask before system-software install, GUI launch, shell-startup edit, or client-config edit outside repo.
- Firefox confirmation stays. Never sideload into profile or auto-grant capability.
- Token stays private. Never run
ff-mcp connection --show-tokenin captured tool output. - Never commit token, print token, paste token, or bind MCP outside loopback.
- Do not run
ff-mcp serve. Firefox starts native host.
Setup
-
Check OS, Firefox 150+, Python 3.14,
uv. -
Run
uv tool install --force .. -
If command missing: run
uv tool dir --bin; use absolute binary. Ask beforeuv tool update-shell. -
Run
ff-mcp profiles --json. -
Show profiles. Ask user for exact path.
-
Ask before Firefox launch.
-
Run:
ff-mcp setup --profile "/exact/profile/path" --install-addon --json -
User confirms Firefox install. User opens popup and presses Start.
-
Snap/Flatpak may show portal prompt. User approves.
-
User privately runs
ff-mcp connection --show-tokenand setsFF_MCP_TOKEN. -
Configure chosen client from runbook. Ask before external config write.
-
Verify tool list,
browser_tabs, approvedREAD, thenbrowser_revoke.
No profile found: user opens about:profiles, copies Root Directory, gives exact path.
Launch fails: run --download-addon; give XPI path. User installs through about:addons → gear →
Install Add-on From File….
Checks
UV_CACHE_DIR=/tmp/ff-mcp-uv-cache uv sync --locked --group dev
UV_CACHE_DIR=/tmp/ff-mcp-uv-cache uv run ruff check .
UV_CACHE_DIR=/tmp/ff-mcp-uv-cache uv run ruff format --check .
UV_CACHE_DIR=/tmp/ff-mcp-uv-cache uv run pytest -q
node --test tests/background.test.js tests/content.test.js tests/policy.test.js tests/rule-model.test.js
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.
- 3d ago First seen · 52 lines · 544 tokens per session scan A 37add7c48350
ff-mcp AGENTS.md is an instructions file published in the GitHub repository complynx/ff-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 544 tokens to every session, about $0.0027 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 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).
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.
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.