wolfpack AGENTS.md

Repository instructions for Wolfpack, whose EDC system supplies generated architectural context for coding agents.

In plain words
What is it for?
Use them at the start of work in the repository to read the context index and follow the authoritative routing and policy manifest.
Why use it?
They tell the agent where to find routing rules, project invariants, and information about which other modules may be affected.

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/almogdepaz/wolfpack/agents-md
Clone the repo
git clone --depth 1 https://github.com/almogdepaz/wolfpack

Made for: Codex, OpenCode.

Per session 70 This file is loaded in full into every session.
When invoked 70 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.00070 $0.00070
Opus 5 $0.00035 $0.00035
Sonnet 5 $0.00014 $0.00014
Haiku 4.5 $0.00007 $0.00007

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

Security

Grade A, and why

wolfpack 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 · 8 lines

What it actually says

Wolfpack EDC Agent Entrypoint

This repo ships deep architectural context generated by EDC.

Runtime mode: advisory; unmatched paths warn-allow.

Read edc-context/index.md first for routing, invariants, and cross-module blast radius. Use edc-context/manifest.json as the authoritative routing/policy contract.

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 · 8 lines · 70 tokens per session scan A 03d012d87a20

Subscribe to this mod's changes

wolfpack AGENTS.md is an instructions file published in the GitHub repository almogdepaz/wolfpack (39 stars, last pushed 2d ago), licensed MIT. It adds 70 tokens to every session, about $0.0003 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.