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/advocate-cloud-solutions/filevine-mcp/agents-mdgit clone --depth 1 https://github.com/Advocate-Cloud-Solutions/filevine-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/advocate-cloud-solutions/filevine-mcp/agents-md)<a href="https://agentmods.dev/instructions/advocate-cloud-solutions/filevine-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/advocate-cloud-solutions/filevine-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.1 | $0.01908 | $0.01908 |
| Opus 5 | $0.00954 | $0.00954 |
| Sonnet 5 | $0.00382 | $0.00382 |
| Haiku 4.5 | $0.00191 | $0.00191 |
Grade A, and why
filevine-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 5d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Setup, build, test, and operating instructions for coding agents and operators working with filevine-mcp.
If you are an LLM agent (Claude Code, Cursor, Aider, etc.) opening this repo, read this file first. If you are a human running this MCP for the first time, this is also the fastest path from zero to a working install.
What this repo is
A single-tenant MCP (Model Context Protocol) server that wraps the Filevine and Lead Docket APIs as Claude-callable tools. Stdio transport. TypeScript. Node 20+.
The server runs on the same machine as the MCP client (Claude Desktop, Claude Code, Cowork, etc.) and talks directly to api.filevine.io (Filevine) and the Lead Docket API using the user's own credentials.
There is no central server, no broker, no gateway. One Filevine org = one MCP process.
Prerequisites
- Node.js 20 or newer (
node --versionmust reportv20.xor higher) - npm 10+ (ships with Node 20)
- A Filevine seat with API access. There is no free sandbox — you need either:
- A paid Filevine seat with API permissions granted by your Org Admin, or
- A Certified Partner Integration (CPI) sandbox if you're a Filevine partner
- (Optional) Lead Docket access if you want the Lead Docket tools enabled
Step 1 — Obtain Filevine credentials
You need five values from Filevine:
FILEVINE_CLIENT_ID— provided by Filevine when you request API access (contact your Filevine account manager or partner contact)FILEVINE_CLIENT_SECRET— paired with the client_idFILEVINE_PAT— a Personal Access Token you generate yourself:- In Filevine, go to Org Admin → Personal Access Tokens
- Click "Generate new PAT"
- Name it (e.g.
clio-mcp-local) - Copy the token immediately — it is shown only once
FILEVINE_USER_ID— your numeric Filevine user ID (visible in Org Admin)FILEVINE_ORG_ID— your numeric Filevine org ID (visible in Org Admin)
For Lead Docket (optional), you additionally need:
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.
- 5d ago First seen · 209 lines · 1,908 tokens per session scan A cfd2b9590cb6
filevine-mcp AGENTS.md is an instructions file published in the GitHub repository Advocate-Cloud-Solutions/filevine-mcp (0 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 1,908 tokens to every session, about $0.0095 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).
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.
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).
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.
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.
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.