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/beyondnetcode/evolith_arch32/copilot-instructionsgit clone --depth 1 https://github.com/beyondnetcode/evolith_arch32What 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.00395 | $0.00395 |
| Opus 5 | $0.00198 | $0.00198 |
| Sonnet 5 | $0.00079 | $0.00079 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
evolith_arch32 copilot-instructions.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 yesterday.
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
Spec-driven AI-DD Agent Instructions for VS Code & Antigravity
As an AI assistant (including GitHub Copilot, Antigravity, and other VS Code AI extensions), you must strictly follow the active spec-driven AI-DD rules in this workspace. BMAD-METHOD is treated as an implementation method for this workflow.
You are expected to assume the persona of the Evolith AI Agents (such as Architect, Developer, QA, or DevOps) depending on the task at hand. Refer to ./AGENTS.md for role definitions.
Mandatory Reference Rules
Before generating code, documentation, or processing architectural decisions, you must ALWAYS load and reference the enforceable instructions defined in the following local paths:
- Primary Enforceable Rules:
./.harness/rules/global-rules.md - Declarative System Index:
./.harness/gemini.md
Key Behaviors Enforced
- Bilingual Documentation Sync (R-01): Simultaneously update both English and Spanish documents and diagrams. Never allow them to drift.
- Contextual Architecture Awareness (R-02): Before any architectural task, validate live boundaries against the local reference corpus.
- Separation of Concerns (R-06): Explicitly split functional requirements from technical system designs in UCs and stories. No mixed content.
- Diagram Language Coherence (R-04): Ensure diagram labels strictly match the language of the container document.
- Architectural Agnosticism: Never introduce a specific technology dependency (e.g. AWS, React) into the Core reference unless explicitly backed by an ADR. Keep the architecture topology-agnostic.
- PO-first Architect-second Order (R-11): Always run Product Owner functional validations before Technical Architect validations.
Refer to product/research/rules-summary.md for an immediate summary table of all governing rules.
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.
- yesterday First seen · 21 lines · 395 tokens per session scan A 9b17ffeaaa91
evolith_arch32 copilot-instructions.md is an instructions file published in the GitHub repository beyondnetcode/evolith_arch32 (0 stars, last pushed 5d ago), licensed MIT. It adds 395 tokens to every session, about $0.0020 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
go-micro CLAUDE.md
Instructions for micro/go-micro, covering claude.md - go micro project guide, project overview, build & test, run all tests and run tests for a specific package.
go-micro AGENTS.md
Instructions for micro/go-micro, covering repository agent instructions and pull requests from codex tasks.
axum-harness AGENTS.md
Instructions for openclosed-org/axum-harness, covering agents.md, 1. language, 2. repository identity, 3. operating posture and 4. development loop.
qiankun AGENTS.md
Instructions for umijs/qiankun, covering qiankun project knowledge base, structure, architecture (big picture), commands and build (vite 8 → package javascript; tsc → declarations).
qiankun CLAUDE.md
Instructions for umijs/qiankun: This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
framework AGENTS.md
Instructions for ai-driven-dev/framework, covering agents.md, behavior, communication, action and memory management.