Borrowing it
Nothing to install: this file belongs to banksynchq/banksync-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/banksynchq/banksync-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/banksynchq/banksync-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/banksynchq/banksync-mcp/agents-md)<a href="https://agentmods.dev/instructions/banksynchq/banksync-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/banksynchq/banksync-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.01525 | $0.01525 |
| Opus 5 | $0.00763 | $0.00763 |
| Sonnet 5 | $0.00305 | $0.00305 |
| Haiku 4.5 | $0.00153 | $0.00153 |
Grade A, and why
banksync-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 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Instructions for AI coding agents working on this repository.
Repo Structure
banksync-mcp/
├── typescript/ # npm package: @banksync/mcp
│ ├── src/index.ts # CLI entry — spawns mcp-remote with API key
│ ├── src/index.test.ts
│ ├── README.md # npm-specific README (SEO optimized for npmjs.com)
│ ├── package.json # pnpm, vitest, oxlint, tsc
│ └── CHANGELOG.md
├── python/ # PyPI package: banksync-mcp
│ ├── banksync_mcp/
│ │ ├── __init__.py
│ │ └── server.py # Async stdio↔HTTP bridge via mcp SDK
│ ├── tests/
│ ├── README.pypi.md # PyPI-specific README (SEO optimized, no HTML)
│ ├── pyproject.toml # uv, pytest, ruff
│ └── CHANGELOG.md
├── .github/workflows/
│ ├── ci.yml # CI: lint + typecheck + test + build (push/PR to main)
│ ├── publish-npm.yml # Publish @banksync/mcp to npm (on release)
│ └── publish-pypi.yml # Publish banksync-mcp to PyPI (on release)
├── server.json # MCP server registry metadata (28 tools)
├── docs/
│ ├── TOOLS.md # End-user tool reference
│ ├── ARCHITECTURE.md # System architecture
│ └── AGENTS.md # Guide for agents *using* BankSync tools
└── README.md
What This Repo Is
Thin MCP clients (Node.js + Python) that bridge stdio ↔ https://mcp.banksync.io. No business logic — just auth validation and protocol forwarding. The remote server (separate repo: banksync-workspace) hosts the actual 28-tool MCP server.
Dev Commands
TypeScript (typescript/)
pnpm install # install deps
pnpm test # vitest run
pnpm lint # oxlint src/
pnpm typecheck # tsc --noEmit
pnpm check # lint + typecheck + test
pnpm build # tsc → dist/
Python (python/)
uv sync # install deps + create venv
uv run pytest -v # run tests
uv run ruff check . # lint
uv run ruff check --fix . # auto-fix lint issues
uv build # build sdist + wheel
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 · 133 lines · 1,525 tokens per session scan A b374f565f86e
banksync-mcp AGENTS.md is an instructions file published in the GitHub repository banksynchq/banksync-mcp (2 stars, last pushed 4mo ago), licensed MIT. It adds 1,525 tokens to every session, about $0.0076 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
CopilotTraining typescript.instructions.md
Instructions for MSBart2/CopilotTraining, covering typescript development standards, type definitions, type safety, generics and union types.
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).