Borrowing it
Nothing to install: this file belongs to imbenrabi/Financial-Modeling-Prep-MCP-Server. 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/imbenrabi/Financial-Modeling-Prep-MCP-Server/main/AGENTS.mdgit clone --depth 1 https://github.com/imbenrabi/Financial-Modeling-Prep-MCP-ServerWrote 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/imbenrabi/financial-modeling-prep-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/imbenrabi/financial-modeling-prep-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/imbenrabi/financial-modeling-prep-mcp-server/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/imbenrabi/financial-modeling-prep-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/imbenrabi/financial-modeling-prep-mcp-server/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.00614 | $0.00614 |
| Opus 5 | $0.00307 | $0.00307 |
| Sonnet 5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
Financial-Modeling-Prep-MCP-Server 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 9d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Intent Layer
Sparse hierarchy of files capturing non-obvious architectural knowledge — pitfalls, anti-patterns, invariants — that agents cannot infer from reading code alone.
Design Principles
- Progressive Disclosure — Start with minimum context; drill into detail via downlinks as needed
- Token Efficiency — Each file under 600 words; if obvious from code, delete it
- LCA Optimization — Place shared knowledge at lowest common ancestor; never duplicate across siblings
- Hierarchical Loading — When a node loads, all ancestors load too (T-shaped view)
Maintenance Rules
- If you change behavior documented in an AGENTS.md, update that file in the same PR
- If you add a new major directory with distinct concerns, add an AGENTS.md and wire it into navigation
Authoring Constraints
- Under 600 words per file
- No facts derivable from reading code
- No teaching/procedural content (that goes in GUIDE.md if needed)
- Positive framing in Key Rules, negative in Anti-patterns
Control Flow Scoring
| Points | Criterion |
|---|---|
| +0 | Pure procedural step (code shows it) |
| +1 | Ordering dependency code enforces |
| +2 | Non-obvious ordering code does NOT enforce |
| +1 | Failure blast radius beyond immediate operation |
| +1 | Side-effect an agent wouldn't expect |
| +1 | Environment-dependent behavior |
Score 0-1: Delete. Score 2: Keep gotcha sentence. Score 3-4: FLOW.md. Score 5: Inline in AGENTS.md.
Navigation
| Node | Non-obvious Knowledge |
|---|---|
docs/src/AGENTS.md |
Startup sequence dependencies, custom Fastify app pitfall |
docs/src/api/AGENTS.md |
API key as query param (never headers), token precedence |
docs/src/tools/AGENTS.md |
Never-throw pattern, global tool name uniqueness |
docs/src/toolception-adapters/AGENTS.md |
Session cache key formula, session-config transport, module adapter constraints |
docs/src/server-mode-enforcer/AGENTS.md |
Singleton init order, fail-fast on invalid toolsets |
docs/src/endpoints/AGENTS.md |
Server-card registry coupling, schema/runtime divergence |
docs/tests/smoke/AGENTS.md |
Smoke test requirements: build first, SSE parsing, global session state |
docs/GUIDE.md |
Procedural guides for adding tools, modules, and tool sets |
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.
- 9d ago First seen · 49 lines · 614 tokens per session scan A 90b67fd2ed37
Financial-Modeling-Prep-MCP-Server AGENTS.md is an instructions file published in the GitHub repository imbenrabi/Financial-Modeling-Prep-MCP-Server (143 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 614 tokens to every session, about $0.0031 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-30.
Other instructions, from other repositories
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.
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 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).
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).
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.
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.