Borrowing it
Nothing to install: this file belongs to OpenCoven/psyche-build. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/OpenCoven/psyche-build/main/AGENTS.mdgit clone --depth 1 https://github.com/OpenCoven/psyche-buildWrote 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/opencoven/psyche-build/agents-md)<a href="https://agentmods.dev/instructions/opencoven/psyche-build/agents-md"><img src="https://agentmods.dev/badge/instructions/opencoven/psyche-build/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.
<a href="https://agentmods.dev/instructions/opencoven/psyche-build/agents-md"><img src="https://agentmods.dev/badge/instructions/opencoven/psyche-build/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.01695 | $0.01695 |
| Opus 5.5 | $0.00678 | $0.00678 |
| Sonnet 5.5 | $0.00339 | $0.00339 |
| Haiku 4.5 | $0.00169 | $0.00169 |
Grade A, and why
psyche-build 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 28d 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Psyche Build agent guide
This file applies to the entire repository. A more specific AGENTS.md may narrow these rules for its subtree. Human instructions and repository policy take precedence over this guide.
Repository role
Psyche Build is OpenCoven's coding cockpit and product client. It owns user-facing cockpit behavior and product-local composition around projects, panes, terminals, tmux sessions, worktrees, branches, optional provider integrations, and platform clients.
Psyche Build does not own the durable OpenCoven identity or orchestration protocol:
OpenCoven/psycheowns canonical familiar, task, lane, run, lease, approval, action, receipt, recovery, and compatibility semantics.- The Coven daemon owns process and PTY execution, project-boundary enforcement, and authoritative runtime events.
- Psyche Build consumes those contracts through versioned adapters. It must not direct-read Psyche's database, duplicate canonical protocol state, or infer authority/completion from a UI selection, tmux pane, process, path, worktree, branch, provider session, or GitHub issue.
- Issue #253 owns the future immutable Psyche profile pin and compatibility canary. Until that lands, do not claim Psyche protocol conformance.
Planning and evidence contract
| Surface | Owns | Must not become |
|---|---|---|
| GitHub outcome issues, milestones, and Project #11 | Public outcomes, owners, priority, train, risk, acceptance gates, and externally legible status | A runtime identity model or proof that a user path works |
| GitHub sub-issues and issue dependencies | Implementation tasks under an outcome and their real ordering | Familiar, task, run, lane, action, or receipt identity |
| Pull requests | Reviewable implementation slices and exact-head proof | Evidence that an entire user path works merely because unit tests pass |
| Specs and plans | Design intent, decisions, and historical reasoning | Executable backlog or proof that behavior shipped |
| Acceptance records | Runtime observations tied to immutable source and artifacts | Unbounded logs, screenshots without provenance, or maintainer memory |
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.
- 28d ago Changed · +52 tokens per session 9e5e91d2218d
- 2mo ago First seen · 105 lines · 1,643 tokens per session scan A c565bfab7047
psyche-build AGENTS.md is an instructions file published in the GitHub repository OpenCoven/psyche-build (3 stars, last pushed 4d ago), licensed MIT. It adds 1,695 tokens to every session, about $0.0068 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.
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).
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.
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).
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 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.