agentweave AGENTS.md

A set of instructions for AI agents working on issues in the AgentWeave codebase. It describes the expected steps from reading an issue through testing, opening a pull request, and deployment checks.

In plain words
What is it for?
Use it when implementing GitHub issues in Python, TypeScript, or Go projects, including running tests, creating branches, committing changes, and preparing pull requests.
Why use it?
It gives agents a consistent development process and makes the issue's acceptance criteria the measure of completion.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/arniesaha/agentweave/agents-md
Clone the repo
git clone --depth 1 https://github.com/arniesaha/agentweave

Made for: Codex, OpenCode.

Per session 519 This file is loaded in full into every session.
When invoked 519 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00519 $0.00519
Opus 5 $0.00260 $0.00260
Sonnet 5 $0.00104 $0.00104
Haiku 4.5 $0.00052 $0.00052

Measured 2d ago against content hash 82dd6e876c3c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agentweave 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.

AGENTS.md · 55 lines

What it actually says

AgentWeave — Autonomous Execution Protocol

For Sub-Agents

When assigned a GitHub issue to implement:

  1. Branch: git checkout -b fix/issue-{NUMBER}
  2. Understand: Read the issue acceptance criteria — that is your definition of done
  3. Implement: Make the code changes
  4. Test:
    • Python: cd sdk/python && pip install -e ".[dev]" && pytest
    • TypeScript: cd sdk/js && npm ci && npx jest --verbose
    • Go: cd sdk/go && go test ./... -v
  5. Commit: fix(scope): description (#NUMBER) — follow conventional commits
  6. Push & PR: Push branch, open PR referencing the issue
  7. Comment on issue: what was changed, any caveats, PR link
  8. Do NOT merge — Nix handles merge + deploy

Nix Post-Merge Checklist

After merging a PR:

  1. Run scripts/deploy.sh
  2. Run scripts/verify.sh
  3. If both pass: close issue with comment linking to Grafana dashboard
  4. If either fails: reopen issue, comment with failure details and logs

Definition of Done (for any issue)

  • Code implemented and tests passing
  • scripts/deploy.sh exits 0
  • scripts/verify.sh exits 0 (all checks green)
  • Issue closed with deploy confirmation comment

Environment Reference

Resource Address
Proxy (nix) 192.168.1.70:30400
Proxy (max) 192.168.1.70:30401
Tempo OTLP endpoint 192.168.1.70:30418
Docker registry localhost:5000
K8s namespace agentweave
Grafana dashboard UID agentweave-overview

Commit Message Convention

type(scope): description (#ISSUE)

Types: fix, feat, chore, docs, refactor, test

Scopes: proxy, sdk-py, sdk-js, sdk-go, dashboard, k8s, ci

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.

  1. 2d ago First seen · 55 lines · 519 tokens per session scan A 82dd6e876c3c

Subscribe to this mod's changes

agentweave AGENTS.md is an instructions file published in the GitHub repository arniesaha/agentweave (11 stars, last pushed 19d ago), licensed MIT. It adds 519 tokens to every session, about $0.0026 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-30.