Borrowing it
Nothing to install: this file belongs to sabbour/agentweaver. 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/sabbour/agentweaver/dev/AGENTS.mdgit clone --depth 1 https://github.com/sabbour/agentweaverWrote 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/sabbour/agentweaver/agents-md)<a href="https://agentmods.dev/instructions/sabbour/agentweaver/agents-md"><img src="https://agentmods.dev/badge/instructions/sabbour/agentweaver/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/sabbour/agentweaver/agents-md"><img src="https://agentmods.dev/badge/instructions/sabbour/agentweaver/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.00661 | $0.00661 |
| Opus 5.5 | $0.00264 | $0.00264 |
| Sonnet 5.5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
agentweaver 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 1mo 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Agentweaver is developed with Squad, a team of named AI agents (Trinity, Tank,
Morpheus, Smith, Link, Seraph, Scribe, and others), and welcomes contributions from AI
agents — including GitHub's @copilot coding agent. If you are an AI agent (Copilot,
Claude, Cursor, or any other tool) that just cloned this repo, start here.
Process
CONTRIBUTING.md → "AI agent contributions"
is the full process doc — read it before making changes. It covers the issue-driven
lifecycle (issue → branch → PR → review → merge), the label-based Squad automation, the
reviewer-rejection protocol, rubber-ducking, the auditable decisions inbox
(.squad/decisions/inbox/), and docs-as-you-go (docs are part of the definition of done,
not a follow-up). This file is a pointer, not a replacement — don't skip the source.
For the dev → release → main model and release/maintenance branching, see
CONTRIBUTING.md → "Branch Topology".
Build & test
The exact per-area build/test commands live in
CONTRIBUTING.md → "Testing" (and are mirrored by the CI
workflow). Run only the suite(s) relevant to what you changed; use the commands there
rather than guessing, so the two don't drift.
Release invariant
Never cut a release unless npm run release:plan succeeds against current
origin/dev. The command intentionally blocks when a published release
preparation was not forward-ported to dev; run
npm run release:sync-dev -- <release-preparation-sha> on a short-lived branch,
merge it to dev, and rerun the plan. Do not bypass or manually reconcile the
version mirrors.
Diagram impact gate
Whenever documentation changes introduce, update, invalidate, consolidate, or remove an
architectural/process visual, consider the on-demand
docs-diagram-audit workflow before the
change is complete. Use the full audit for repository-wide or cross-page impact, and
record why the single-diagram docs-diagram-pitch/docs-diagram-iterate path is sufficient
when no catalog audit is needed. Product code and behavior are visual/factual references
only; diagram work remains docs-only.
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.
- 1mo ago Changed · +9 lines · +90 tokens per session a5f429ba0f0f
- 1mo ago Changed · +10 lines · +123 tokens per session 1c4c935a83c5
- 1mo ago First seen · 34 lines · 448 tokens per session scan A 333eafc6d905
agentweaver AGENTS.md is an instructions file published in the GitHub repository sabbour/agentweaver (7 stars, last pushed today), licensed MIT. It adds 661 tokens to every session, about $0.0026 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
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core 10, parameterized queries, migration strategy.
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).