secedgar-mcp-server: Instructions file for Codex

AGENTS.md

secedgar-mcp-server AGENTS.md is an instructions file for Codex, OpenCode from cyanheads/secedgar-mcp-server. It costs 30,594 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for a server that provides read-only access to SEC EDGAR filings, company data, and XBRL financial records. SEC EDGAR is the U.S. government database of company filings, while XBRL is a structured format for financial data.

In plain words
What is it for?
Building or changing tools that query company filings and financial information through the server's MCP interface.
Why use it?
They give coding agents the project's required rules for handling requests, errors, logging, and stored data safely.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions .claude-plugin; mentions CLAUDE.md.

This is cyanheads/secedgar-mcp-server's own configuration. It tells Codex and OpenCode how to work on secedgar-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything secedgar-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to cyanheads/secedgar-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.

Copy the file
curl -O https://raw.githubusercontent.com/cyanheads/secedgar-mcp-server/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/cyanheads/secedgar-mcp-server

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for secedgar-mcp-server AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/cyanheads/secedgar-mcp-server/agents-md/github.svg)](https://agentmods.dev/instructions/cyanheads/secedgar-mcp-server/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/cyanheads/secedgar-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/secedgar-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.

agentmods 80×15 button for secedgar-mcp-server AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/cyanheads/secedgar-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/secedgar-mcp-server/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30,594 This file is loaded in full into every session.
When invoked 30,594 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.30594 $0.30594
Opus 5.5 $0.12238 $0.12238
Sonnet 5.5 $0.06119 $0.06119
Haiku 4.5 $0.03059 $0.03059

Measured 4d ago against content hash 721bab2e5af0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

secedgar-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 4d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 440 lines

How it starts

The opening of the file, as written. The whole thing — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Protocol

Server: secedgar-mcp-server Version: 0.15.13 Framework: @cyanheads/mcp-ts-core ^0.13.15 Engines: Bun ≥1.4.0, Node ≥24.0.0 MCP SDK: @modelcontextprotocol/server ^2.3.1 Zod: ^4.6.5

Query SEC EDGAR filings, XBRL financials, and company data through MCP. Read-only, no API keys required. Full design: docs/sec-edgar-mcp-design.md.

Read the framework docs first: node_modules/@cyanheads/mcp-ts-core/CLAUDE.md contains the full API reference — builders, Context, error codes, exports, patterns. This file covers server-specific conventions only.


Core Rules

  • Logic throws, framework catches. Tool/resource handlers are pure — throw on failure, no try/catch. Plain Error is fine; the framework catches, classifies, and formats. Use error factories (notFound(), validationError(), etc.) when the error code matters.
  • Use ctx.log for request-scoped logging. No console calls. Attach operation-specific fields with withExtra(ctx, { … }) — RequestContext is closed, so a bare { ...ctx, field } spread no longer type-checks.
  • Use ctx.state for tenant-scoped storage. Never access persistence directly.
  • Ask for missing input with return ctx.requestInput(...), reading the answers back through ctx.inputs when the handler is re-entered. Never await a caller mid-handler.
  • Secrets in env vars only — never hardcoded.
  • Cut noise. Add only what earns its place: no speculative generality, no guards for states the framework already prevents (Zod-validated params, classified errors), no abstraction until a third caller proves it, no option nothing sets.
  • Close the loop on issues. When implementing work tracked by a GitHub issue, comment on the issue with what landed and close it. Do both — a comment without a close leaves stale issues open; a close without a comment leaves no record of what shipped. The comment is for future readers — state the concrete changes, not the conversation that produced them.

Read the full file on GitHub · 440 lines

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.

  1. 4d ago Changed · +1 lines · +2,731 tokens per session 721bab2e5af0
  2. 8d ago Changed · +1 lines · +4,195 tokens per session 7f448165fe8e
  3. 18d ago Changed · +10 lines · +4,889 tokens per session 8cd7c2faa137
  4. 27d ago Changed · +3 lines · +1,600 tokens per session a5307379f6e8
  5. 28d ago Changed · +8 lines · +1,855 tokens per session 5f1b4d82e3b2
  6. 1mo ago Changed · +4 lines · +1,083 tokens per session 36d7e3065658
  7. 1mo ago Changed · +3 lines · +393 tokens per session b4c99e40aab1
  8. 1mo ago Changed · +7 lines · +2,338 tokens per session 28cdf338f15b
  9. 1mo ago Changed 9fa09ccefaaa
  10. 1mo ago First seen · 403 lines · 11,510 tokens per session scan A 76d3f05c25b7

Subscribe to this mod's changes

secedgar-mcp-server AGENTS.md is an instructions file published in the GitHub repository cyanheads/secedgar-mcp-server (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 30,594 tokens to every session, about $0.1224 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.

Related

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).

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,549 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens