Borrowing it
Nothing to install: this file belongs to ratulotron/sc-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ratulotron/sc-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/ratulotron/sc-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/ratulotron/sc-mcp/claude-md)<a href="https://agentmods.dev/instructions/ratulotron/sc-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ratulotron/sc-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.00692 | $0.00692 |
| Opus 5 | $0.00346 | $0.00346 |
| Sonnet 5 | $0.00138 | $0.00138 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
sc-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 7d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintaining sc-mcp
This server is a thin wrapper around the Scalable Capital sc CLI. Its main
maintenance burden is staying in sync with sc, which is pre-1.0 and can
change its command surface between minor versions.
When a new sc version ships
Run the machine-readable capability dump and compare it against what the server assumes:
sc --version
sc capabilities --json | python3 -m json.tool | less
- Version. Compare
data.versiontoSUPPORTED_SC_VERSIONinsrc/sc_mcp/server.py. If the major.minor changed, work through the rest of this list, then bump the constant. - Commands. Diff
data.commandsagainst the 8 tools inserver.py(broker.overview,broker.holdings,broker.transactions,broker.transaction.details,broker.analytics,broker.quote,broker.search,broker.security-news). New read-only broker command → consider adding a tool. Renamed/removed → update or drop the tool. - Flags. For each wrapped command, re-check its
--help. If a flag the server passes was renamed or removed, fix the tool and its case inARGV_CASESintests/test_sc_mcp.py. - Exit codes / envelope.
data.exit_codesanddata.outputdescribe the error and JSON-envelope contract_run_screlies on. If they change, adjust error handling. - Update the Compatibility line in
README.mdandSUPPORTED_SC_VERSION.
Before committing
uv run ruff check . && uv run ruff format --check . && uv run pytest
Versioning the change
SemVer on the tools (see README → Versioning): tool removed/renamed = MAJOR, tool/optional-param added = MINOR, fix = PATCH. Then:
git tag -a vX.Y.Z -m "vX.Y.Z" && git push origin vX.Y.Z
gh release create vX.Y.Z --title vX.Y.Z --notes "..."
Then rebuild the Claude Desktop bundle (its manifest pins both version and the
@vX.Y.Z git ref):
# bump version + git ref in mcpb/manifest.json, then:
npx -y @anthropic-ai/mcpb pack mcpb dist/sc-mcp.mcpb
gh release upload vX.Y.Z dist/sc-mcp.mcpb
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.
- 7d ago First seen · 66 lines · 692 tokens per session scan A fb6d64a95570
sc-mcp CLAUDE.md is an instructions file published in the GitHub repository ratulotron/sc-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 692 tokens to every session, about $0.0035 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).
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).
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.