Borrowing it
Nothing to install: this file belongs to shigechika/jquants-mcp. 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/shigechika/jquants-mcp/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/shigechika/jquants-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/shigechika/jquants-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/shigechika/jquants-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/shigechika/jquants-mcp/copilot-instructions.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.02798 | $0.02798 |
| Opus 5 | $0.01399 | $0.01399 |
| Sonnet 5 | $0.00560 | $0.00560 |
| Haiku 4.5 | $0.00280 | $0.00280 |
Grade A, and why
jquants-mcp copilot-instructions.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 7d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository overview
jquants-mcp is an MCP (Model Context Protocol) server exposing Japanese
stock market data from the J-Quants API v2 to AI assistants. It is
stdio-only and built on the official mcp SDK's FastMCP
(from mcp.server.fastmcp import FastMCP, in src/jquants_mcp/server.py) —
not the standalone fastmcp package, which was dropped together with the
HTTP/OAuth surface (#568). Other core modules: client.py (httpx async
client, rate limiting, retry, pagination), cache/store.py (two-tier SQLite
cache), allowlist.py (the JQUANTS_ALLOWED_EMAILS gate), crypto.py
(AES-256-GCM), db/users.py / db/users_firestore.py (per-user encrypted
key storage), request_context.py (per-request plan contextvar),
oauth_login.py (the login subcommand's PKCE flow against J-Quants' own
Cognito pool — this obtains the upstream API key and is unrelated to
authenticating end users of this server).
The server authenticates nobody and binds no socket. On Cloud Run an
oauth2-proxy sidecar in front of mcp-stdio serve verifies the user and
spawns one stdio child process per session, injecting the verified email as
the JQUANTS_MCP_USER environment variable (read by server.py's
_current_user_id()). What remains in this repo's scope is what the server
does with that injected identity: per-user client/plan state and per-user
encrypted API keys (SQLite locally, Firestore on Cloud Run). See CLAUDE.md
for the full architecture breakdown — read it before reviewing changes to
server.py, crypto.py, or cache/store.py.
Build & validate
uv sync --dev
uv run ruff check src/ tests/
uv run ruff format --check --exclude _version.py src/ tests/
uv run pytest -v
This mirrors .github/workflows/ci.yml: a lint job (ruff check + ruff format --check) and a test job matrixed over Python 3.10–3.13, plus a
separate test-windows job on Python 3.12 (kept as its own job, not folded
into the matrix, specifically to preserve stable test (3.x) check names for
branch protection while still catching Windows-only breakage such as file
encoding/path issues at PR time). Note CI's format check uses --check --exclude _version.py; the plain ruff format src/ tests/ from CLAUDE.md
is the local auto-fix form of the same rule — don't treat a diff that only
needs ruff format (no --check) run locally as a CI mismatch.
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.
- 7d ago First seen · 191 lines · 2,798 tokens per session scan A f2704273969b
jquants-mcp copilot-instructions.md is an instructions file published in the GitHub repository shigechika/jquants-mcp (2 stars, last pushed 6d ago), licensed MIT. It adds 2,798 tokens to every session, about $0.0140 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
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).
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.
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.