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/accd/verchestra/agents-mdgit clone --depth 1 https://github.com/accd/verchestraWhat 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.01140 | $0.01140 |
| Opus 5 | $0.00570 | $0.00570 |
| Sonnet 5 | $0.00228 | $0.00228 |
| Haiku 4.5 | $0.00114 | $0.00114 |
Grade A, and why
verchestra 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verchestra Repository Instructions
Mission and current status
Verchestra is a verified AI software-delivery harness. It is currently
0.0.0-qualification: T77 is complete and the declared qualification chain is
fully verified. That is not a release. The signed promote-or-reject decision the
contract (docs/qualification/RELEASE-DECISION-CONTRACT.md) requires has been
made: it is a signed reject — a recorded hold —
(docs/qualification/release-decision-1.0.0.md, #18). The candidate is fit to
keep operating as 0.0.0-qualification and is not promoted to 1.0.0; a promote
round would decide on a fresh candidate with its own decision file, after the
tracked promote-readiness work lands. The verchestra npm package is published at
0.0.0-qualification, so a public installer exists and may be described
truthfully; do not claim production readiness or a 1.0 release.
These instructions are provider-neutral and sufficient after a clean clone. Git and tracked repository artifacts are authoritative; chat history, provider memory, IDE integrations, MCP servers, and installed skills are optional.
Start every task
- Run
git status --short --branchandgit rev-parse HEAD. - Read the issue or request, this file, and the closest scoped
AGENTS.md. - Read
docs/architecture.md,ROADMAP.md, and any active feature.specs/features/<slug>/handoff.md. - Use
corepack pnpm agent:contextwhen available to confirm status, required reads, active work, and repository gates. - Identify the canonical source before editing. Generated projections and build output are never canonical.
Closest scoped instructions refine these rules for their subtree. They must not contradict or relax this file.
Repository map
Read docs/repository-map.md before changing package boundaries. Inward
dependency direction is contracts → domain → application; adapters may depend
on those inward packages but not sibling adapters. apps/vestra-cli is the
composition root. apps/site is a build-time documentation projection.
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.
- 2d ago First seen · 114 lines · 1,140 tokens per session scan A 8e2f89ef475e
verchestra AGENTS.md is an instructions file published in the GitHub repository accd/verchestra (5 stars, last pushed 3d ago), licensed Apache-2.0. It adds 1,140 tokens to every session, about $0.0057 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.
Other instructions, from other repositories
ai-engineering-skills AGENTS.md
Instructions for tmusser/ai-engineering-skills, covering agent instructions, route-first context loading and quality standards.
scrub-mcp AGENTS.md
AGENTS.md instructions for zombat/scrub-mcp, covering s.c.r.u.b. agent instructions, prime directive, prohibited actions (the bash ban), division of labor and context gathering rules (map-then-navigate).
nextclaw AGENTS.md
Instructions for Peiiii/nextclaw, covering nextclaw ai 常驻内核, 产品愿景, 沟通与推进, 深思与目标模式 and 协作与 git 安全.
medusa CLAUDE.md
Claude Code instructions for Pantheon-Security/medusa, covering medusa - medusa security scanning, critical: release gate — do not skip, 4. security hardening tests (must show: all pass), critical: bash sandbox and project overview.
slipway AGENTS.md
Instructions for signalridge/slipway, covering slipway agent principles, user owns the process, investigate before clarifying, report, do not certify and maintain the whole surface.
nobrainer-tech-skills copilot-instructions.md
Instructions for nobrainer-tech/nobrainer-tech-skills: The fifteen canonical Agent Skills are under skills/; retired predecessors exist only in Git history. Read the relevant skills/ /SKILL.md before changing a skill.