Borrowing it
Nothing to install: this file belongs to BradMorphsters/tuskledger-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/BradMorphsters/tuskledger-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/BradMorphsters/tuskledger-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/bradmorphsters/tuskledger-mcp/agents-md)<a href="https://agentmods.dev/instructions/bradmorphsters/tuskledger-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/bradmorphsters/tuskledger-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.01179 | $0.01179 |
| Opus 5 | $0.00589 | $0.00589 |
| Sonnet 5 | $0.00236 | $0.00236 |
| Haiku 4.5 | $0.00118 | $0.00118 |
Grade A, and why
tuskledger-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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Working memory for AI assistants (Claude Code, Cursor, Cowork, etc.) operating on this repository. Read this first.
What this project is
tuskledger-mcp is a Model Context Protocol
server that runs locally on a user's machine and gives their AI
assistant typed access to data in their
Tusk Ledger install. It's a thin
adapter — the actual finance data and logic live in the main
tuskledger app; this
package just translates MCP tool calls into HTTP requests against
that app's local FastAPI backend (http://127.0.0.1:8000 by default).
Local-first, no exceptions. Nothing here calls out to the network.
The only HTTP destination is 127.0.0.1. If you find yourself
writing a request to a non-localhost URL, stop and ask the user.
Permission boundaries
Safe to do without asking
- Add a new tool that wraps an existing read-only backend endpoint
- Improve a tool description (LLM tool-selection accuracy depends on these)
- Tighten input schemas (
additionalProperties: false, required fields, etc.) - Add tests
- Update the README, CHANGELOG, or AGENTS.md
Ask the user first
- Add a tool that performs a write/mutation
- Bump the
mcpSDK version - Change the JSON shape of any tool's output (it's a contract for the LLM caller)
- Change the env-var names (users have these wired in their MCP client config)
Never do without explicit user instruction
- Add a tool that performs a destructive operation (delete a transaction, remove a connected account, rotate keys, etc.)
- Add a non-localhost HTTP destination
- Capture, log, or transmit Plaid tokens, balances, or transaction details outside the user's machine
- Change the package name (it's published as
tuskledger-mcp)
Repo structure
tuskledger-mcp/
├── README.md ← user-facing install + usage docs
├── AGENTS.md ← you are here
├── CHANGELOG.md
├── LICENSE ← MIT
├── pyproject.toml ← package metadata, deps, console script
├── tuskledger_mcp/
│ ├── __init__.py ← __version__
│ ├── __main__.py ← `python -m tuskledger_mcp` entry
│ ├── client.py ← TuskLedgerClient: sync httpx wrapper
│ └── server.py ← TOOLS list + _dispatch + build_server + serve_stdio
└── tests/
└── test_server.py ← dispatch + schema invariants
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 · 123 lines · 1,179 tokens per session scan A 752334427c7c
tuskledger-mcp AGENTS.md is an instructions file published in the GitHub repository BradMorphsters/tuskledger-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 1,179 tokens to every session, about $0.0059 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
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.