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/lesleslie/spline-mcp/agents-mdgit clone --depth 1 https://github.com/lesleslie/spline-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/lesleslie/spline-mcp/agents-md)<a href="https://agentmods.dev/instructions/lesleslie/spline-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/lesleslie/spline-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.00298 | $0.00298 |
| Opus 5 | $0.00149 | $0.00149 |
| Sonnet 5 | $0.00060 | $0.00060 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
spline-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.
What it actually says
Repository Guidelines
Project Structure & Module Organization
spline_mcp/contains the MCP server package, including scene management tools, API clients, and runtime-state helpers.settings/stores configuration defaults, andtests/should mirror the package structure for object, material, event, and state coverage.- Keep ecosystem and operator guidance in root docs rather than local scripts.
Build, Test, and Development Commands
uv sync --group devinstalls development dependencies.- Use the documented local server commands for stdio or HTTP smoke tests.
uv run pytestruns the test suite.uv run ruff check spline_mcp testsanduv run ruff format spline_mcp testscover linting and formatting.
Coding Style & Naming Conventions
- Use explicit type hints, validated scene payloads, and small tool handlers.
- Keep modules snake_case and public tool responses structured and predictable.
Testing Guidelines
- Add tests for scene queries, state changes, and API error handling.
- Prefer mocked Spline responses over brittle live integration tests unless the case explicitly requires end-to-end verification.
Commit & Pull Request Guidelines
- Use focused commits such as
fix(materials): preserve color normalization. - PRs should describe affected tools, commands run, and any runtime-state changes.
Security & Configuration Tips
- Never commit tokens or workspace credentials.
- Validate object identifiers and external URLs strictly.
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 · 35 lines · 298 tokens per session scan A 8161b8f7ceb4
spline-mcp AGENTS.md is an instructions file published in the GitHub repository lesleslie/spline-mcp (4 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 298 tokens to every session, about $0.0015 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
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).
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.
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).