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 instructions/wenqingyu/ralphy-openspec/agents-mdgit clone --depth 1 https://github.com/wenqingyu/ralphy-openspecWrote 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/instructions/wenqingyu/ralphy-openspec/agents-md)<a href="https://agentmods.dev/instructions/wenqingyu/ralphy-openspec/agents-md"><img src="https://agentmods.dev/badge/instructions/wenqingyu/ralphy-openspec/agents-md.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.00483 | $0.00483 |
| Opus 5 | $0.00242 | $0.00242 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
ralphy-openspec 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.
What it actually says
Ralphy-OpenSpec Agent Instructions (OpenCode)
You are an AI coding assistant operating in a repository that uses:
- OpenSpec for spec-driven development (
openspec/specs/+openspec/changes/) - Ralph loop for iterative execution (the same prompt may be repeated)
Golden rules
- Treat
openspec/specs/as the source of truth (current behavior). - Treat
openspec/changes/<change-name>/as the proposed/active change. - Only mark tasks complete when verification (tests) passes.
- Keep changes small, deterministic, and test-backed.
Workflow
1) Plan (PRD -> OpenSpec)
When asked to plan or create specs:
- Read
openspec/project.mdand relevant files inopenspec/specs/. - Create a new change folder under
openspec/changes/<change-name>/with:proposal.md(why/what/scope/non-goals/risks)tasks.md(checklist with test plan notes)specs/**/spec.md(deltas: ADDED/MODIFIED/REMOVED)
- Ensure requirements use MUST/SHALL and each requirement has at least one scenario.
2) Implement (Tasks -> Code)
When asked to implement:
- Identify the active change folder under
openspec/changes/. - Implement tasks in order from
tasks.md. - Run tests frequently and fix failures.
- Update the checkbox status in
tasks.mdonly when verified.
3) Validate (Acceptance criteria)
When asked to validate:
- Map scenarios/acceptance criteria to tests/commands.
- Run the project test command (commonly
npm test). - Report which requirements are proven and what gaps remain.
4) Archive
When asked to archive:
- Prefer
openspec archive <change-name> --yesif OpenSpec CLI is available. - Otherwise, move the change into
openspec/archive/and ensureopenspec/specs/reflects the final state.
Ralph loop completion promise
If you are being run in a loop, only output this exact text when ALL tasks are complete and tests are green:
TASK_COMPLETE
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.
- 3d ago First seen · 47 lines · 483 tokens per session scan A 11735ebcb560
ralphy-openspec AGENTS.md is an instructions file published in the GitHub repository wenqingyu/ralphy-openspec (182 stars, last pushed 7mo ago), licensed BSD-3-Clause. It adds 483 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.
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).
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.
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.
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.
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).
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.