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/contextweaver/sensitivitygit clone --depth 1 https://github.com/dgenio/contextweaverWhat 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.00121 | $0.00121 |
| Opus 5 | $0.00060 | $0.00060 |
| Sonnet 5 | $0.00024 | $0.00024 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
contextweaver sensitivity.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
Sensitivity Enforcement — Security-Grade Code
This module enforces data classification and redaction in the context pipeline. Treat all changes as security-sensitive:
- Never weaken defaults. The default sensitivity floor and default drop action are deliberately conservative.
- Extra review scrutiny required. Changes here affect what data reaches the LLM.
- Do not refactor for "simplicity." The current structure exists to enforce
safety invariants. See
docs/agent-context/invariants.mdfor rationale.
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 · 15 lines · 121 tokens per session scan A 6b3d8e3ff2c7
contextweaver sensitivity.instructions.md is an instructions file published in the GitHub repository dgenio/contextweaver (9 stars, last pushed 2d ago), licensed Apache-2.0. It adds 121 tokens to every session, about $0.0006 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
kindex CLAUDE.md
Instructions for jmcentire/kindex, covering kindex — knowledge graph for ai-assisted workflows, running tests, all tests, specific module and with coverage.
ChainWeaver AGENTS.md
Instructions for dgenio/ChainWeaver, covering chainweaver — agent instructions, 1. project identity, 2. domain vocabulary, 3. repository layout and 4. core invariants.
ChainWeaver copilot-instructions.md
Instructions for dgenio/ChainWeaver, covering copilot instructions — chainweaver, scoped guidance, review-critical rules, executor guardrails and vocabulary.
ChainWeaver testing.instructions.md
Instructions for dgenio/ChainWeaver, covering testing instructions — chainweaver, framework, structure, fixtures and coverage patterns.
ChainWeaver python-source.instructions.md
Instructions for dgenio/ChainWeaver, covering python source instructions — chainweaver, module conventions, pydantic patterns, exception patterns and export rules.
ChainWeaver chainweaver.instructions.md
Instructions for dgenio/ChainWeaver: Also read the nearest path-scoped AGENTS.md for the subtree you are changing — the index is in AGENTS.md § 11.