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 skills/bostonorange/claude-code-framework/mock-endpointnpx skills add BostonOrange/claude-code-framework --skill mock-endpointgit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWhat 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.00041 | $0.02728 |
| Opus 5 | $0.00020 | $0.01364 |
| Sonnet 5 | $0.00008 | $0.00546 |
| Haiku 4.5 | $0.00004 | $0.00273 |
Grade A, and why
mock-endpoint scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s "https://api.example.com/endpoint?param=value" -H "Authorization: Bearer $TOKEN" How it starts
The opening of the file, as written. The whole thing — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mock Endpoint
Define, mock, and test external API integrations safely. Creates a contract-first development workflow where external dependencies are fully described before any code touches a real service.
Usage
/mock-endpoint sl-transport-api # Mock an external API from scratch
/mock-endpoint sl-transport-api departures # Mock a specific endpoint group
/mock-endpoint --from-code # Scan codebase for existing API calls and generate mocks
/mock-endpoint --list # List all defined mocks
Why This Exists
When AI implements features that call external APIs:
- It can't test against real services (rate limits, auth, side effects)
- It may guess wrong about request/response shapes
- Tests that hit real endpoints are flaky and slow
- Wiring up incorrectly against production is dangerous
This skill creates a contract layer between your code and external services. The AI develops against the contract, tests against mocks, and the real service is only connected after human review.
Core Concepts
Contract File
The source of truth for what an external API looks like. Lives in .claude/skills/mock-endpoint/references/{service-name}.md.
Mock Fixture
Static request/response pairs generated from the contract. Used in tests.
Mock Server (optional)
A lightweight local server that serves mock responses. Used for manual testing and dev server integration.
Integration Wrapper
A thin abstraction layer around the external API call. In production it hits the real service; in tests it hits the mock.
Process
1. Define the Contract
If user provides docs or a URL, extract the API surface. If the API is already called in the codebase, scan for it.
Via Context7 (for known libraries/SDKs)
If the external service has an official SDK or client library, fetch documentation using the /fetch-docs skill pattern (resolve-library-id then get-library-docs) for endpoint signatures, auth patterns, and response shapes. Use fetched docs to populate the contract accurately instead of guessing.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 357 lines · 41 tokens per session scan A 91961cf838e9
mock-endpoint is a skill published in the GitHub repository BostonOrange/claude-code-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 2,728 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…