Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/bmbouter/mcp-dropbox-sign/claude-mdgit clone --depth 1 https://github.com/bmbouter/mcp-dropbox-signWrote 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/bmbouter/mcp-dropbox-sign/claude-md)<a href="https://agentmods.dev/instructions/bmbouter/mcp-dropbox-sign/claude-md"><img src="https://agentmods.dev/badge/instructions/bmbouter/mcp-dropbox-sign/claude-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.01797 | $0.01797 |
| Opus 5 | $0.00898 | $0.00898 |
| Sonnet 5 | $0.00359 | $0.00359 |
| Haiku 4.5 | $0.00180 | $0.00180 |
Grade A, and why
mcp-dropbox-sign CLAUDE.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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mcp-dropbox-sign Project Context
This file provides context and instructions for all Claude sessions working on this project.
Overview
mcp-dropbox-sign is a Model Context Protocol (MCP) server providing access to the Dropbox Sign API via 10 resource areas using FastMCP. The development uses a Ralph Wiggum autonomous TDD loop with /loop 5m for rapid iteration.
Project Structure
mcp-dropbox-sign/
├── .env # Credentials (NOT committed; user provides)
├── .env.example # Template for .env
├── .venv/ # Virtual environment (NOT committed)
├── src/mcp_dropbox_sign/
│ ├── __init__.py
│ ├── config.py # Load API credentials from .env
│ ├── client.py # DropboxSignClient (httpx-based)
│ └── resources/
│ ├── __init__.py # Wires up all resources
│ ├── signature_requests.py # Resource 1
│ ├── templates.py # Resource 2
│ ├── teams.py # Resource 3
│ ├── accounts.py # Resource 4
│ ├── events.py # Resource 5
│ ├── documents.py # Resource 6
│ ├── signers.py # Resource 7
│ ├── reports.py # Resource 8
│ ├── bulk.py # Resource 9
│ └── workflows.py # Resource 10
├── tests/
│ ├── __init__.py # Empty; marks tests as package
│ ├── conftest.py # Pytest fixtures; mocks httpx layer
│ ├── test_signature_requests.py # Resource 1 tests
│ ├── test_templates.py # Resource 2 tests
│ └── ... # More test files
├── scripts/
│ ├── verify_api.py # One-shot credential check (manual)
│ ├── score.sh # Bash scorecard (runs each iteration)
│ └── commit.sh # Smart commit (runs each iteration)
├── CLAUDE.md # This file (project context)
├── LOOP.md # Loop-specific directives
├── pyproject.toml # Project metadata
└── README.md
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 · 217 lines · 1,797 tokens per session scan A 5c92d5645eea
mcp-dropbox-sign CLAUDE.md is an instructions file published in the GitHub repository bmbouter/mcp-dropbox-sign (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,797 tokens to every session, about $0.0090 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
ZATCA AGENTS.md
AGENTS.md instructions for SallaApp/ZATCA: See CLAUDE.md for the full guide. Quick facts.
ayunis-legal-mcp CLAUDE.md
Instructions for ayunis-core/ayunis-legal-mcp, covering legal mcp - architecture and development guide, project overview, architecture, directory structure and key components.
korean-firefighter-law-mcp CLAUDE.md
Claude Code instructions for ssd7830-cmyk/korean-firefighter-law-mcp, covering korean-firefighter-law-mcp, a. 답변 규칙 — 기억이 아니라 이 저장소의 코드가 근거다, b. mcp 도구 사용 and c. 작업 규칙.
uae-regulations-registry AGENTS.md
AGENTS.md instructions for nshield-security/uae-regulations-registry, covering agents.md — instructions for ai agents, what this repo contains, preferred entry points, json schema (data/regulations.json) and stable urls.
spain-ai-kit CLAUDE.md
Instructions for aplaceforallmystuff/spain-ai-kit, a project described as: MCP servers connecting AI applications to Spanish government open data and legal infrastructure.
law-mcp CLAUDE.md
Claude Code instructions for finalchild/law-mcp, covering claude.md, build and development commands, architecture overview, core components and key integration points.