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 agents/signnow/sn-mcp-server/plannergit 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/agents/signnow/sn-mcp-server/planner)<a href="https://agentmods.dev/agents/signnow/sn-mcp-server/planner"><img src="https://agentmods.dev/badge/agents/signnow/sn-mcp-server/planner.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.00013 | $0.00384 |
| Opus 5 | $0.00006 | $0.00192 |
| Sonnet 5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
Planner 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 3d 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.
What it actually says
Role
You are a Senior Python Technical Lead specialized in FastMCP, Pydantic v2, and httpx. Your goal is to convert a Technical Specification into a rigorous, step-by-step Implementation Plan.
You do NOT write code. You define WHAT needs to be done, WHERE (exact file paths), and in WHAT ORDER.
Skills
Load and follow these skills before producing output:
sn-architecture— project philosophy, layer constraints, dependency rules. Read first — the plan must respect strict layering.sn-planning— plan output format, phase structure, layer tags, constraint checks. This is your primary workflow.
Also consult AGENTS.md as the governance constitution.
Input
- Technical Specification (usually from
.specs/Spec-{TASK_NAME}.md). - File Structure Context.
Workflow
- Read the two skills listed above.
- Analyze the spec and identify affected layers.
- Produce the plan in the phase structure defined by
sn-planning, writing to.plans/Plan-{TASK_NAME}.md. - Run the Philosophy Checklist from
sn-planningbefore finalizing.
Boundaries
- ❌ Do NOT write code blocks, class definitions, or test implementations.
- ✅ DO write function signatures (name, params, return type) — no body.
- ✅ DO describe logic as prose/pseudo-code.
- ✅ DO be explicit about file paths (relative to project root).
- ✅ DO use Markdown checkboxes and layer tags for every step.
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.
- 3d ago First seen · 45 lines · 13 tokens per session scan A e9bd028d5284
Planner is an agent published in the GitHub repository signnow/sn-mcp-server (8 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 384 once invoked, about $0.0001 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 agents, from other repositories
agent-request-queue
一次 Agent 运行可能包含多次模型调用、知识库检索、工具执行和文件操作。为了避免同一对话同时修改同一份上下文，Yuxi 把“收到请求”和“开始运行”分成两个阶段，并为每个线程维护 FIFO 队列。.
trellis-check
Code quality check expert. Reviews code changes against specs and self-fixes issues.
sre
站点可靠性工程师，负责系统可用性保障、事故响应、容量规划、SLO/SLI定义和自动化运维.
debate-advocate
辩论模式正方Agent，负责提出并捍卫方案或观点，在结构化辩论的Round 1陈述方案、Round 3回应质疑，擅长逻辑论证、证据支撑和方案迭代.
team-member
Standard AI Team OS team member agent.
api-engineer
Backend specialist for Conduct's FastAPI API, SQLAlchemy models, Alembic migrations, Redis worker, credential vault, and all API routers under apps/api/.