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/signnow/sn-mcp-server/agents-mdgit clone --depth 1 https://github.com/signnow/sn-mcp-serverWrote 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/signnow/sn-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/signnow/sn-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/signnow/sn-mcp-server/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 | $0.02766 | $0.02766 |
| Opus 5 | $0.01383 | $0.01383 |
| Sonnet 5 | $0.00553 | $0.00553 |
| Haiku 4.5 | $0.00277 | $0.00277 |
Grade A, and why
sn-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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SignNow MCP Server
Stateless translation layer between AI agents and the SignNow API. Every tool response is curated through tools/models.py — never pass raw API JSON. Omit nulls, empty lists, and metadata the agent won't act on.
Agent-first
100% of the code is agent-written. When something comes out wrong, the fix belongs in automatic feedback (lint rules, type constraints, tests, import-linter contracts), not only in the code. Prose guidance in this file is the fallback, not the first line of defence.
Before closing a task where the human corrected you, ask: "what rule would have prevented this?" and propose adding it.
Self-check pyramid
Three layers, each bounded by what stays fast for its trigger. The point is to catch in the same conversation what CI would catch minutes later.
| Trigger | What runs | Where defined | Budget |
|---|---|---|---|
git commit |
ruff-format + ruff on staged files; mypy src/ (~1 s); pytest tests/unit (~4 s) |
.pre-commit-config.yaml (stages: [pre-commit]) |
<10 s |
git push |
full pytest (unit + integration + api) with coverage ≥70 %; lint-imports full-graph boundary check |
.pre-commit-config.yaml (stages: [pre-push]) |
<30 s |
PR / push to main |
everything above + full-repo ruff + mypy + diff-coverage ≥80 % vs origin/main, posted as sticky PR comment |
.github/workflows/ci.yml |
<10 min |
Install hooks with pre-commit install --install-hooks (SessionStart hook does this automatically in a fresh Claude Code session). Bypass with --no-verify only in genuine emergencies — if a hook is consistently wrong, fix the hook.
Enforced invariants
Rules in ## Boundaries below that can be checked mechanically, are — an edit that violates one fails immediately:
signnow_client → sn_mcp_serveris forbidden —import-lintercontract inpyproject.toml.sn_mcp_server.tools → starlette/uvicornis forbidden — same contract set.- Every MCP tool returns a curated Pydantic model from
sn_mcp_server.tools—tests/unit/sn_mcp_server/test_tool_response_shapes.pyparametrizes overregister_tools()and fails on rawdict/list/Anyreturns. - Static types are clean —
mypy src/instrictmode, zero errors. New# type: ignorerequires an inline reason. - Lint is clean repo-wide —
ruff check src/ tests/(no diff-only escape hatch). New# noqarequires a reason. - Coverage doesn't regress — global ≥70 % (
[tool.coverage.report] fail_under), patch ≥80 % (CIdiff-cover).
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.
- 4d ago First seen · 105 lines · 2,766 tokens per session scan A 2c381b6398bd
sn-mcp-server AGENTS.md is an instructions file published in the GitHub repository signnow/sn-mcp-server (8 stars, last pushed 1mo ago), licensed MIT. It adds 2,766 tokens to every session, about $0.0138 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
docker-swarm-mcp AGENTS.md
AGENTS.md instructions for KHAEntertainment/docker-swarm-mcp, covering docker-swarm-mcp development guidelines, active technologies, project structure, project structure and commands.
Kokoro-FastAPI AGENTS.md
AGENTS.md instructions for remsky/Kokoro-FastAPI, covering agents.md, layout, commands, conventions and gotchas.
geolens CLAUDE.md
Claude Code instructions for geolens-io/geolens: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
substack-gateway-oss CLAUDE.md
Claude Code instructions for jakub-k-slys/substack-gateway-oss, covering claude.md, commands, install dependencies (dev included, all workspace members), run the server (dev mode with reload) and lint.
igniter-js GEMINI.md
Gemini CLI instructions for felipebarcelospro/igniter-js, covering 1. identity and profile, 2. about the igniter.js monorepo, 3. personality and communication, 4. lia's core responsibilities (the 4 pillars) and 5. technical guidelines and methodology.
Huntable-CTI-Studio AGENTS.md
AGENTS.md instructions for dfirtnt/Huntable-CTI-Studio, covering agents.md, orientation, local context, prompt-injection alerting and change-type quick reference.