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/abl030/slskd-mcp/claude-mdgit clone --depth 1 https://github.com/abl030/slskd-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/abl030/slskd-mcp/claude-md)<a href="https://agentmods.dev/instructions/abl030/slskd-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/abl030/slskd-mcp/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.02831 | $0.02831 |
| Opus 5 | $0.01416 | $0.01416 |
| Sonnet 5 | $0.00566 | $0.00566 |
| Haiku 4.5 | $0.00283 | $0.00283 |
Grade A, and why
slskd-mcp 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
slskd MCP Server
Auto-generated MCP server for the slskd API v0. Tools generated from spec/openapi.json (OpenAPI 3.0.1, 70 paths, 93 operations). When slskd updates their API, pull a new spec and re-run the generator.
Rules
- Never manually edit
generated/server.py. Fix the generator or templates instead. spec/openapi.jsonis the single source of truth. All type information, parameter names, and endpoint structure come from the spec.- Test against Docker, not production. Use
docker/docker-compose.ymlfor integration testing. - Always use
nix develop -cas the default wrapper for repo commands. - Testing must be automated. Every feature/fix needs a pytest suite or equivalent.
- Add tests with features. When adding new functionality, always write automated tests in the same change.
- Sprint progress lives in CLAUDE.md. When work spans multiple sessions, document sprint plans, progress, and outcomes here.
- Reference
research/mcp-server-best-practices.mdbefore making generator decisions. These are hard-won lessons from 4 prior MCP builds (pfSense 677 tools, UniFi 286 tools, Lidarr 235 tools, Loki 42 tools). - Every new feature must include both tests AND docstring updates. Tool docstrings are the primary way consuming LLMs discover and understand tools. If a feature isn't described in docstrings, it doesn't exist to the LLM. When adding or changing functionality: (a) add/update unit tests, (b) add/update integration tests where the feature touches the generated server, and (c) ensure tool docstrings clearly describe what the tool does, its parameters, expected return values, and any workflow hints.
Repository Structure
spec/openapi.json # slskd OpenAPI 3.0.1 spec (input)
generator/ # Python generator
__main__.py # Entry point: python -m generator
loader.py # Load and parse the OpenAPI spec
naming.py # Convert method+path to tool names
schema_parser.py # Extract parameter types from schemas
context_builder.py # Build template context, assign modules
codegen.py # Render templates and write output
templates/
server.py.j2 # FastMCP server template
generated/
server.py # The MCP server (never hand-edit)
tests/ # Unit + integration tests
research/ # Best practices, API notes
docker/ # Integration test infrastructure
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 · 184 lines · 2,831 tokens per session scan A a3b1ff5477fe
slskd-mcp CLAUDE.md is an instructions file published in the GitHub repository abl030/slskd-mcp (1 stars, last pushed 6mo ago), licensed MIT. It adds 2,831 tokens to every session, about $0.0142 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
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).
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 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).
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.