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/srbryers/slope/slope-api-referencenpx skills add srbryers/slope --skill slope-api-referencegit clone --depth 1 https://github.com/srbryers/slopeWhat 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.00084 | $0.00870 |
| Opus 5 | $0.00042 | $0.00435 |
| Sonnet 5 | $0.00017 | $0.00174 |
| Haiku 4.5 | $0.00008 | $0.00087 |
Grade A, and why
slope-api-reference 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SLOPE API Reference
Reference for using SLOPE's 12 MCP tools effectively. Covers the context tier decision tree, tool categories, common patterns, and all known gotchas.
File Map
| File | Purpose |
|---|---|
SKILL.md |
This file — overview, context tiers, tool categories |
gotchas.md |
All 12 MCP gotchas with examples and workarounds |
references/mcp-tools.md |
All 12 tools with input schemas and output shapes |
references/execute-cookbook.md |
Common execute() patterns for scoring, analysis, roadmaps |
references/search-guide.md |
Module-by-module search guide with special cases |
scripts/execute-examples.js |
Composable JS snippets for execute() calls |
Context Tier Decision Tree
Always use the lowest tier that answers your question:
Need to know which package owns a feature?
→ L0: Read CODEBASE.md headers (~2k tokens)
Need function signatures, CLI commands, guards?
→ L1: Read full CODEBASE.md (~5k tokens)
→ Or: search({ module: 'map' })
Need to find a specific implementation?
→ L1.5: context_search("query") or search({ module: 'map', query: '...' })
Need implementation detail, debugging, modifying code?
→ L2: Read tool on specific files (unbounded tokens)
MCP Tool Categories
Core Tools (always available)
| Tool | Purpose |
|---|---|
search |
Discover API functions, filter by module/query |
execute |
Run JS in sandbox with full SLOPE API pre-injected |
context_search |
Semantic search (embeddings) with grep fallback |
Store-Backed Tools (require .slope/slope.db)
| Tool | Purpose |
|---|---|
session_status |
Current session info |
acquire_claim |
Claim a ticket/area for the sprint |
check_conflicts |
Detect overlapping claims |
store_status |
Store health check |
Testing Tools (require .slope/slope.db)
| Tool | Purpose |
|---|---|
testing_session_start |
Begin a manual testing session |
testing_session_finding |
Record a test finding |
testing_session_end |
End testing session with summary |
testing_session_status |
Current testing session state |
testing_plan_status |
Test plan completion status |
What ships with it
5 files 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 · 94 lines · 84 tokens per session scan A 06334749ca79
slope-api-reference is a skill published in the GitHub repository srbryers/slope (6 stars, last pushed 3d ago), licensed MIT. It adds 84 tokens to every session and 870 once invoked, about $0.0004 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 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…