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/trustabl/trustabl-rules/claude-mdgit clone --depth 1 https://github.com/trustabl/trustabl-rulesWhat 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.02479 | $0.02479 |
| Opus 5 | $0.01239 | $0.01239 |
| Sonnet 5 | $0.00496 | $0.00496 |
| Haiku 4.5 | $0.00248 | $0.00248 |
Grade A, and why
trustabl-rules CLAUDE.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 3d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions for Claude — Trustabl detection rules
These instructions apply to any work on the detection rule packs in this repository. The packs here are pulled by the Trustabl engine at scan time; the rule schema and predicate implementations, plus the per-rule test harness, live in that engine repository. Links below labeled "engine repo" point there.
Engine/rules split — read this first
- Rules (the
.yamlpacks) live here. - Schema, predicates, evaluator, loader, and the per-rule fire/silent test
table live in the engine repo under
internal/rules/. - The engine validates rules against its own copy of these packs at
testdata/rules-fixture/(the test fixture). Until the test harness is pointed directly at this repository, a rule change here must be mirrored into the engine'stestdata/rules-fixture/with its fire/silent test cases, or the engine'sTestPolicyRules_AllRulesCoveredguard will not cover it. - There is no
go testto run in this repo — it has no Go. Validation runs in the engine repo (go test ./...).
Required reading order before editing
- Schema reference (engine repo):
internal/rules/schema.yaml— authoritative field reference. README.md— conventions in this repo.- The closest existing rule to what's being asked for — pattern example.
Do not skip step 1.
Hard rules
- Never invent YAML keys. The schema is closed (
KnownFields(true)). If a field you want does not exist in the engine'sinternal/rules/schema.go, extending the schema is a four-file change in the engine repo (schema.go + predicates.go + evaluator.go + schema.yaml), gated by amanifest.yamlschema_versionbump here. Make the engine changes in one commit. - Never change a rule's
idafter it has shipped. IDs are external identifiers; downstream consumers cite them, and the engine folds the resolved pack into the scanScanID. - Never duplicate a rule ID across files. The loader rejects this at startup.
- Never widen
applies_toacross SDKs casually. A rule'sexplanation/fixtext is usually SDK-specific. Addingopenai_toolto a Claude-SDK rule (or vice versa) makes the user-facing text lie. If a cross-SDK pattern is genuinely needed, author a separate rule under that SDK's category (<sdk>_sdk/<topic>.yaml) with framing that matches the target SDK. - Never write rules at
infoseverity. Reserved.
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.
- 3d ago First seen · 189 lines · 2,479 tokens per session scan A 6f1e5199c740
trustabl-rules CLAUDE.md is an instructions file published in the GitHub repository trustabl/trustabl-rules (24 stars, last pushed 7d ago), licensed Apache-2.0. It adds 2,479 tokens to every session, about $0.0124 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.
Other instructions, from other repositories
ii-agent AGENTS.md
Instructions for Intelligent-Internet/ii-agent, covering ii-agent contributor guide, quick start, repository map, mandatory rules and architecture.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
InvestSkill GEMINI.md
Instructions for yennanliu/InvestSkill, covering investskill — gemini cli setup & usage guide, installation & setup, quick start, navigate to the investskill directory and start gemini cli (loads gemini.md automatically).
sortie copilot-instructions.md
Instructions for sortie-ai/sortie, covering sortie coding & review standards, 1. layered imports (downward only; violation is critical), 2. concurrency safety, 3. workspace path safety (critical: security boundary) and 4. persistence (sqlite).
crust AGENTS.md
Instructions for chenxin-yan/crust, covering tests, documentation, changesets, agent skills and issue tracker.
she-love-me CLAUDE.md
Instructions for 863401402/she-love-me, covering claude.md and 唯一工作流.