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/dgenio/chainweaver/testsgit clone --depth 1 https://github.com/dgenio/ChainWeaverWhat 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.00201 | $0.00201 |
| Opus 5 | $0.00101 | $0.00101 |
| Sonnet 5 | $0.00040 | $0.00040 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
ChainWeaver tests.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
Tests
File boundary
tests/helpers.py— shared Pydantic schemas and tool functions.tests/conftest.py— pytest fixtures that compose objects fromhelpers.py.
Do not merge these files. Do not put schemas in conftest.py or fixtures in
helpers.py.
Framework rules
- pytest only. No
unittest.TestCase, noself.assertEqual. - Plain
assertstatements (pytest rewrites them). - No mocking of internal ChainWeaver classes unless testing integration boundaries.
- Test both success and failure/error paths.
Organization
- Unit tests grouped by module (
test_{module}.py). - Integration tests grouped by scenario.
- Test classes grouped by scenario (e.g.,
TestSuccessfulExecution).
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 · 29 lines · 201 tokens per session scan A d7ee282b6dca
ChainWeaver tests.instructions.md is an instructions file published in the GitHub repository dgenio/ChainWeaver (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 201 tokens to every session, about $0.0010 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
wet-mcp AGENTS.md
Instructions for n24q02m/wet-mcp, covering agents.md - wet-mcp, cau truc, lenh thuong dung, mise shortcuts and cau hinh quan trong.
maidan CLAUDE.md
Instructions for david-engelmann/maidan, covering agent guide, 30-second orientation, read order, the cluster model in one paragraph and pr workflow (the short version).
luxembourg-mcp CLAUDE.md
Instructions for amirdaraee/luxembourg-mcp, covering claude.md, commands, hard constraint: zero dependencies, architecture and adding or changing a tool touches five places.
swag-mcp CLAUDE.md
Instructions for jmagar/swag-mcp, covering swag mcp - claude memory reference, project overview, core architecture, key components and common development commands.
datalens-dev-mcp AGENTS.md
Instructions for ADIKANT/datalens-dev-mcp, covering agents.md, scope, read order, local material policy and public change hygiene.
swiss-democracy-mcp CLAUDE.md
Instructions for malkreide/swiss-democracy-mcp, covering claude.md, vor der arbeit, tests, zahlen, die eine aufzählung wiederholen and wenn etwas rot ist.