What is slope-api-reference?

A reference guide for using SLOPE's 12 MCP tools. It explains which search or context level to use, how to run commands, and how to handle sessions, claims, and testing.

Searching project context, writing SLOPE execute calls, managing sessions and claims, checking testing workflows, and debugging MCP errors.

It helps the agent choose the right SLOPE tool and avoid known usage errors when retrieving or changing project information.

How srbryers/slope configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to srbryers/slope. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/srbryers/slope/main/.claude/skills/slope-api-reference/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/srbryers/slope

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/srbryers/slope/slope-api-reference/github.svg)](https://agentmods.dev/skills/srbryers/slope/slope-api-reference)

Your own site

<a href="https://agentmods.dev/skills/srbryers/slope/slope-api-reference"><img src="https://agentmods.dev/badge/skills/srbryers/slope/slope-api-reference/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/srbryers/slope/slope-api-reference"><img src="https://agentmods.dev/badge/skills/srbryers/slope/slope-api-reference.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 870 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00084	$0.00870
Opus 5.5	$0.00034	$0.00348
Sonnet 5.5	$0.00017	$0.00174
Haiku 4.5	$0.00008	$0.00087

Measured 2mo ago against content hash 06334749ca79, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/execute-examples.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.claude/skills/slope-api-reference/SKILL.md · 94 lines

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

Read the full file on GitHub · 94 lines

Files

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.

Changes

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.

2mo ago First seen · 94 lines · 84 tokens per session scan A 06334749ca79

Subscribe to this mod's changes

slope-api-reference is a skill published in the GitHub repository srbryers/slope (6 stars, last pushed 4d ago), licensed MIT. It adds 84 tokens to every session and 870 once invoked, about $0.0003 per session on Opus 5.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.

Building agents Debugging

slope-api-reference next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
slope-api-referencesrbryers/slope	Skill	6	4d ago	MIT	A	84	Claude Code
systematic-debuggingopen-metadata/OpenMetadata	Skill	16k	yesterday	Apache-2.0	A	37	Claude Code
log-error-digestzebbern/claude-code-guide	Skill	4.7k	3d ago	MIT	A	71	Claude Code, Codex
cwv-optimizeradobe/skills	Skill	319	yesterday	Apache-2.0	A	112	Claude Code
ci-fixersipyourdrink-ltd/bernstein	Skill	1.2k	yesterday	Apache-2.0	A	15	Claude Code, Codex
incident-response-incident-responsermyndharis/antigravity-skills	Skill	1.9k	23d ago	MIT	A	36	Claude Code
triaging-web-analytics-supportPostHog/posthog	Skill	41k	today	none	A	151	Claude Code, Codex

slope: Skill for Claude Code