agentmods.dev

slope AGENTS.md

slope AGENTS.md is an instructions file for Codex, OpenCode from srbryers/slope. It costs 536 tokens per session, scanned A, original, MIT.

A repository guide for SLOPE, a framework for tracking software sprints with golf-style terms. It documents commands, connected tools, work stages, task difficulty labels, and commit rules.

In plain words
What is it for?
Use it to view project briefings, validate scorecards, review sprints, classify tickets, and follow the project’s commit and push conventions.
Why use it?
It gives agents a shared way to classify work, record results, review sprint progress, and keep changes organised.

Instructions file for CodexOpenCode

not rated 6 3d ago A scan 536 tokens original MIT
View the source file srbryers/slope
Install

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.

agentmods
npx agentmods add instructions/srbryers/slope/agents-md
Clone the repo
git clone --depth 1 https://github.com/srbryers/slope

Made for: Codex, OpenCode.

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.

agentmods badge for slope AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/srbryers/slope/agents-md.svg)](https://agentmods.dev/instructions/srbryers/slope/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/srbryers/slope/agents-md"><img src="https://agentmods.dev/badge/instructions/srbryers/slope/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 536 This file is loaded in full into every session.
When invoked 536 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00536 $0.00536
Opus 5 $0.00268 $0.00268
Sonnet 5 $0.00107 $0.00107
Haiku 4.5 $0.00054 $0.00054

Measured 3d ago against content hash dbd9771ebe9f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

slope AGENTS.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 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.

AGENTS.md · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

SLOPE Project

This project uses the SLOPE framework for sprint tracking.

Commands

  • slope card — view handicap card
  • slope validate — validate scorecards
  • slope review — generate sprint review
  • slope briefing — pre-round briefing

MCP Tools

A SLOPE MCP server is configured in opencode.json. Two tools:

  • search — discover API functions, types, constants
  • execute — run JS with full SLOPE API in sandbox

Sprint Workflow

  • Pre-Hole: slope briefing for handicap, hazards, gotchas
  • Per-Shot: classify each ticket with approach + result + hazards
  • Post-Hole: slope validate scorecard, slope review, update common-issues

Approach Complexity

  • Driver: risky/new territory
  • Long Iron: multi-package changes
  • Short Iron: standard work
  • Wedge: small tasks
  • Putter: trivial changes

Shot Results

  • In the Hole: perfect execution
  • Green: landed correctly
  • Fairway: clean start, needs finishing
  • Miss directions: over-scoped, under-scoped, wrong approach, drift

Commit Discipline

  • Commit after each file, feature, migration, or bug fix
  • Push after each ticket and every 30 minutes
  • Format: <type>(<ticket>): <summary> (feat/fix/refactor/docs/test/chore)

Codebase Map

SLOPE maintains a codebase map at CODEBASE.md (~5k tokens). Read it before exploring.

  • Run slope map to generate/update
  • Run slope map --check to verify staleness
  • Use search({ module: 'map' }) via MCP for targeted queries

Roadmap Sources

docs/roadmap/project.yaml is the authoring manifest. The files under docs/roadmap/archive/ and docs/roadmap/phases/ are authoritative; docs/backlog/roadmap.json is generated compatibility output.

  • Run slope now, then use its sprint with slope roadmap focus --sprint=N instead of loading the full history
  • Edit the owning YAML bundle, then run slope roadmap compile
  • Run slope roadmap validate-sources and slope roadmap compile --check before committing

Scorecards

Stored in docs/retros/sprint-N.json. See .slope/config.json for configuration.

Read the full file on GitHub · 58 lines

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.

  1. 3d ago First seen · 58 lines · 536 tokens per session scan A dbd9771ebe9f

Subscribe to this mod's changes

slope AGENTS.md is an instructions file published in the GitHub repository srbryers/slope (6 stars, last pushed 3d ago), licensed MIT. It adds 536 tokens to every session, about $0.0027 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.

Planning
Related

Other instructions, from other repositories

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

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens