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/sabbour/agentweaver/copilot-instructionsgit clone --depth 1 https://github.com/sabbour/agentweaverWhat 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.00348 | $0.00348 |
| Opus 5 | $0.00174 | $0.00174 |
| Sonnet 5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
agentweaver 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 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.
What it actually says
Copilot instructions — Agentweaver
You are working in Agentweaver, a repo developed with Squad (a named AI agent
team) that welcomes contributions from AI agents, including GitHub's @copilot. If you
are an AI agent landing here cold, read these entry points before making changes:
CONTRIBUTING.md→ "AI agent contributions" — THE canonical process entry point. Covers the issue-driven lifecycle (issue → branch → PR → review → merge), the reviewer-rejection protocol, rubber-ducking, the decisions inbox, and docs-as-you-go. Read this first. Its "Testing" section has the exact build/test commands per area — use those, don't invent your own. Its "Branch Topology" section is the canonical policy for the activedev → release → mainmodel and future maintenance/queue growth.AGENTS.md— short cross-tool orientation for AI agents (points back to the docs below).specs/README.md— the current product-spec index (area-grouped product stories). Read this when you need product or feature context.RELEASING.md— anything release/versioning/branching related (semver, cutting a release, deploy vs. upgrade vs. release).
Keep documentation part of the definition of done: update docs/guide/ and/or README.md
in the same change when user-facing behavior 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.
- 2d ago First seen · 22 lines · 348 tokens per session scan A 35d446cf8c2e
agentweaver copilot-instructions.md is an instructions file published in the GitHub repository sabbour/agentweaver (5 stars, last pushed 2d ago), licensed MIT. It adds 348 tokens to every session, about $0.0017 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
zeroshot CLAUDE.md
Claude Code instructions for the-open-engine/zeroshot, covering zeroshot: multi-agent coordination engine, 🔴 critical rules, 🔴 general purpose requirement (critical), 🔴 behavioral standards and where to look.
sofagent GEMINI.md
Instructions for KongFangXun/sofagent, covering gemini.md · sofagent gemini cli 适配（薄挂载）, 会话开始时按序加载（四层加载链）, 审计强制（平台无关） and 连接 mcp server.
PuPu CLAUDE.md
Instructions for haoxiang-xu/PuPu, covering gitnexus — code intelligence, always do, never do, resources and cli.
rondoflow CLAUDE.md
Instructions for rondoflow/rondoflow, covering rondoflow, project overview, tech stack, development and setup.
OpenVitamin AGENTS.md
Instructions for fengzhizi715/OpenVitamin, covering agents.md — inference gateway & plugin governance, 1. 项目与技术栈对齐说明, 2. 核心设计原则（core principles）, 2.1 user-in-control（用户始终掌控） and 2.2 gateway-centric（以推理网关为中心）.
plan-forge aci-design.instructions.md
Agent-Computer Interface (ACI) rules — how every forge MCP tool must shape its inputs and outputs so the calling agent can use it reliably. Auto-loads when editing tool definitions or capabilities.