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-setupnpx skills add srbryers/slope --skill slope-setupgit clone --depth 1 https://github.com/srbryers/slopeWrote 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/skills/srbryers/slope/slope-setup)<a href="https://agentmods.dev/skills/srbryers/slope/slope-setup"><img src="https://agentmods.dev/badge/skills/srbryers/slope/slope-setup.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 | $0.00046 | $0.00433 |
| Opus 5 | $0.00023 | $0.00217 |
| Sonnet 5 | $0.00009 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00043 |
Grade A, and why
slope-setup 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.
What it actually says
SLOPE Setup For Codex
Use this when the user wants SLOPE available from an agent harness.
Install Or Update
- Run
slope init --codexfrom the repository root. - If the repo already has SLOPE, run
slope doctor --fixafter init. - Prefer one active Codex hook path:
- project-local:
.codex/hooks.json - user-level:
~/.codex/hooks.json
- project-local:
- Avoid enabling both paths for the same repo unless the user explicitly wants duplicate hook firing.
Verify
- Run
slope doctor. - Run
slope hook list. - Run
python3 -m json.tool .codex/hooks.jsonfor project-local hooks, orpython3 -m json.tool ~/.codex/hooks.jsonfor user-level hooks. - Run
bash -n .codex/hooks/slope-guard.shorbash -n ~/.codex/hooks/slope-guard.sh. - Restart Codex and review
/hooksafter hook changes.
Planning Discovery
When the user asks for a roadmap interview, run slope roadmap interview or slope roadmap interview --agent. If using MCP directly, call search({ module: "init" }) to discover getInitQuestions() and submitInitAnswers().
Explain
Tell the user that the Codex plugin bundle exposes SLOPE skills and MCP metadata under a named SLOPE integration. The bundle also includes metadata-only hook definitions for future Codex plugin-hook support, but the plugin manifest intentionally does not declare hooks because current Codex plugin validation rejects that field. Active guard enforcement uses the stable Codex hooks.json shim installed by slope init --codex while Codex plugin_hooks is under development.
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 · 34 lines · 46 tokens per session scan A d8ea2c3829fd
slope-setup is a skill published in the GitHub repository srbryers/slope (6 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 433 once invoked, about $0.0002 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…