sdp AGENTS.md

Project instructions for the sdp repository, which uses Beads, a command-line issue-tracking system, to manage development work.

In plain words
What is it for?
Use it to find and update issues, run Go build, test, and vet checks, maintain canonical prompts, and finish development sessions.
Why use it?
It defines the required quality checks and session-closing steps so changes are tested, tracked, synchronized, and pushed correctly.

Instructions file for CodexOpenCode

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/fall-out-bug/sdp/agents-md
Clone the repo
git clone --depth 1 https://github.com/fall-out-bug/sdp

Made for: Codex, OpenCode.

Per session 486 This file is loaded in full into every session.
When invoked 486 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.00486 $0.00486
Opus 5 $0.00243 $0.00243
Sonnet 5 $0.00097 $0.00097
Haiku 4.5 $0.00049 $0.00049

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

Security

Grade A, and why

sdp 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 2d 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

What it actually says

Agent Instructions

This project uses bd (beads) for issue tracking. Run bd onboard to get started.

Quick Reference

bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --status in_progress  # Claim work
bd close <id>         # Complete work
bd sync               # Sync with git

Quality Gates

Before pushing code changes:

go build ./...              # must succeed
go test ./...               # must pass
go vet ./...                # no issues

For Go changes, follow the canonical @go-modern skill in prompts/skills/go-modern/SKILL.md and prefer modern stdlib idioms when they preserve behavior.

Canonical Prompt Source

  • Canonical prompts live in prompts/skills/*/SKILL.md and prompts/agents/*.md.
  • .claude/skills and .claude/agents are compatibility symlinks to prompts/*.
  • When updating prompts, edit prompts/* paths as source of truth.

Landing the Plane (Session Completion)

When ending a work session, you MUST complete ALL steps below. Work is NOT complete until git push succeeds.

MANDATORY WORKFLOW:

  1. File issues for remaining work - Create issues for anything that needs follow-up
  2. Run quality gates (if code changed) - Tests, linters, builds
  3. Update issue status - Close finished work, update in-progress items
  4. PUSH TO REMOTE - This is MANDATORY:
    git pull --rebase
    bd sync
    git push
    git status  # MUST show "up to date with origin"
    
  5. Clean up - Clear stashes, prune remote branches
  6. Verify - All changes committed AND pushed
  7. Hand off - Provide context for next session

CRITICAL RULES:

  • Work is NOT complete until git push succeeds
  • NEVER stop before pushing - that leaves work stranded locally
  • NEVER say "ready to push when you are" - YOU must push
  • If push fails, resolve and retry until it succeeds
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. 2d ago First seen · 58 lines · 486 tokens per session scan A dfd1bc396af5

Subscribe to this mod's changes

sdp AGENTS.md is an instructions file published in the GitHub repository fall-out-bug/sdp (19 stars, last pushed 2mo ago), licensed MIT. It adds 486 tokens to every session, about $0.0024 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-30.

Related

Other instructions, from other repositories

ai-control-framework CLAUDE.md

Instructions for sgharlow/ai-control-framework, covering claude code configuration, framework status (v2.0) — verified 2026-07-18, ⚠️ critical: implementation required, mandatory session start procedure and hard stop conditions.

sgharlow/ai-control-framework · 1,577 tokens

code-discipline-skills AGENTS.md

Instructions for eliranpv11/code-discipline-skills, covering code discipline, priority order, 1. think before coding, 2. verify reality before acting and 3. simplicity first.

eliranpv11/code-discipline-skills · 1,801 tokens

umbra AGENTS.md

AGENTS.md instructions for elberacasa/umbra, covering agents.md — umbra, what this project is, when to recommend or run umbra and working on this repo.

elberacasa/umbra · 933 tokens

umbra copilot-instructions.md

Copilot instructions for elberacasa/umbra, a project described as: The trust score for AI-generated code. One command verifies what your coding agent shipped: security findings with file:line evidence, Docker-sandboxed build/boot checks, and claim receipts that catch agents lying about tests.

elberacasa/umbra · 23 tokens

claude-agentic-coding-playbook CLAUDE.md

Instructions for john-wilmes/claude-agentic-coding-playbook, covering agentic coding playbook, quality gates, architecture, dependencies and build and project conventions.

john-wilmes/claude-agentic-coding-playbook · 831 tokens

forgecraft-mcp copilot-instructions.md

Copilot instructions for jghiringhelli/forgecraft-mcp, covering copilot instructions, project identity, code standards, production code standards — non-negotiable and solid principles.

jghiringhelli/forgecraft-mcp · 4,676 tokens