PEDAL: Instructions file for Codex

AGENTS.md

PEDAL AGENTS.md is an instructions file for Codex, OpenCode from krgoodnews/PEDAL. It costs 271 tokens per session, scanned A, original, Apache-2.0.

A set of instructions for PEDAL, a structured software-development workflow covering planning, design documents, implementation, analysis, and completion reports.

In plain words
What is it for?
It helps plan and build features, perform gap analysis, track progress from project files, and maintain the documentation and configuration that guide coding agents.
Why use it?
It keeps work phases, project conventions, and feature changes organized while separating feature work from the main project through Git worktrees.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is krgoodnews/PEDAL's own configuration. It tells Codex and OpenCode how to work on PEDAL itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything PEDAL configures →

Reuse

Borrowing it

Nothing to install: this file belongs to krgoodnews/PEDAL. 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/krgoodnews/PEDAL/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/krgoodnews/PEDAL

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 PEDAL AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/krgoodnews/pedal/agents-md/github.svg)](https://agentmods.dev/instructions/krgoodnews/pedal/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/krgoodnews/pedal/agents-md"><img src="https://agentmods.dev/badge/instructions/krgoodnews/pedal/agents-md/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.

agentmods 80×15 button for PEDAL AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/krgoodnews/pedal/agents-md"><img src="https://agentmods.dev/badge/instructions/krgoodnews/pedal/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 271 This file is loaded in full into every session.
When invoked 271 The same file — it is already loaded in full.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00271 $0.00271
Opus 5.5 $0.00108 $0.00108
Sonnet 5.5 $0.00054 $0.00054
Haiku 4.5 $0.00027 $0.00027

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

Security

Grade A, and why

PEDAL 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 2mo 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 · 17 lines

What it actually says

Agent Instructions

PEDAL workflow

When the user mentions PEDAL, planning, engineering documents, gap analysis, iteration, completion reports, or asks for plan, engineering, do, analyze, iterate, learn, archive, status, next, spec, build, or dev, read and follow .pedal/PEDAL.md.

PEDAL is tool-agnostic. Do not assume Gemini-only slash commands are required. If this agent does not support slash commands, treat natural language requests such as PEDAL plan A_Project user-auth as the equivalent PEDAL action.

Key rules:

  1. Run PEDAL from the workspace root that contains the project repositories.
  2. Use git worktrees for feature work as described in .pedal/PEDAL.md.
  3. After creating a feature worktree, perform feature-specific file operations inside that worktree, not the main project directory.
  4. Infer PEDAL status from worktree and docs/ files; do not create a separate state file.
  5. During Plan, Engineering, Do, and Analyze phases, read docs/wiki/CONVENTIONS.md if it exists.
  6. Keep tool-specific behavior in the relevant adapter file. The shared workflow source of truth is .pedal/PEDAL.md.
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. 2mo ago First seen · 17 lines · 271 tokens per session scan A 3e07403fa27e

Subscribe to this mod's changes

PEDAL AGENTS.md is an instructions file published in the GitHub repository krgoodnews/PEDAL (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 271 tokens to every session, about $0.0011 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.

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 · 9,719 tokens

next.js AGENTS.md

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,461 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,334 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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,792 tokens

generative-ai-for-beginners AGENTS.md

AGENTS.md instructions for microsoft/generative-ai-for-beginners, covering agents.md, project overview, setup commands, initial repository setup and clone the repository.

microsoft/generative-ai-for-beginners · 2,850 tokens