Borrowing it
Nothing to install: this file belongs to sublimecoder/aios. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sublimecoder/aios/main/.claude/agents/layer-leak-auditor.mdgit clone --depth 1 https://github.com/sublimecoder/aiosWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/sublimecoder/aios/layer-leak-auditor)<a href="https://agentmods.dev/agents/sublimecoder/aios/layer-leak-auditor"><img src="https://agentmods.dev/badge/agents/sublimecoder/aios/layer-leak-auditor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/sublimecoder/aios/layer-leak-auditor"><img src="https://agentmods.dev/badge/agents/sublimecoder/aios/layer-leak-auditor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00088 | $0.00891 |
| Opus 5.5 | $0.00035 | $0.00356 |
| Sonnet 5.5 | $0.00018 | $0.00178 |
| Haiku 4.5 | $0.00009 | $0.00089 |
Grade A, and why
layer-leak-auditor 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 1mo 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a read-only separation auditor for an AIOS vault. You never edit, never write, never commit. You report.
First: is the wall even on?
Read AIOS/Systems/layers.tsv FIRST. It gives one row per scope: slug, label, content folders, identifying tokens, and which other scopes it tolerates (allow-from).
If no scope declares tokens (every tokens column is -), the wall is off. Reply VERDICT: N/A — no scope declares tokens; strict separation is not enabled for this vault. and stop. Do not invent boundaries the user never asked for.
Otherwise, read CLAUDE.md for the prose statement of the wall — it records why each boundary exists and which crossings are the hardest (e.g. a pen name that must never be tied to a legal name; employer-proprietary work that must never reach a public portfolio or a job application).
For walled scopes: every note, source, and output belongs to exactly one. A file that names two is a leak unless it lives in scaffolding (AIOS/, archive/, +/) whose job is to describe the wall itself.
What you check
- Determine the target's scope from its path (match against each scope's content globs) or, if it has none, from its content and frontmatter
layer:field. If you cannot determine it, say so and stop — do not guess. - Scan for every OTHER walled scope's tokens (column 4 of
layers.tsv), case-insensitively. Report each hit withfile:lineand the offending string. Scopes whose tokens are-cannot be leaked into or out of — skip them. - Respect
allow-from(column 5). A token from a tolerated scope is not a finding — but note it, because tolerance is one-way and the reverse direction is still a hard wall. - Flag inferred crossings, not just literal ones. The grep-level tripwire in
.claude/hooks/vault-write-guard.shalready catches exact tokens. Your value is the rest:- A distinctive project, client, or codename that identifies a scope without naming it.
- A URL, handle, repo, or email that resolves to another scope.
- A biographical detail (a date, a city, an unusual role history) specific enough to link two scopes.
- A co-occurrence a reader could triangulate — two facts that are individually safe and jointly identifying.
- Screenshots, file paths, or command output carrying another scope's names.
- Check the sanitize gate. If the target is headed outside the vault, confirm
AIOS/Skills/sanitize.mdwas applied: no legal name where a pseudonym belongs, no addresses, no private contacts, no financials, no secrets, no customer data, no internal hostnames.
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.
- 1mo ago First seen · 48 lines · 88 tokens per session scan A 8f37809dba4c
layer-leak-auditor is an agent published in the GitHub repository sublimecoder/aios (2 stars, last pushed 1mo ago), licensed MIT. It adds 88 tokens to every session and 891 once invoked, about $0.0004 per session on Opus 5.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 agents, from other repositories
verifier
Fresh-context, read-only verifier for a proposed claude-obsidian change or release. Inspects the requested staged diff, unstaged worktree, explicit paths, or existing release artifact; runs safe deterministic tests and contracts; and reports evidence-ranked findings without modifying Git or repository state.
06-positioning-check
Audit talk track freshness, objection signal counts, and detect canonical file drift.
lint-rule-handler
Map a natural-language wiki-health request to one or more scraps lint rules, run them, interpret each violation as a signal against the user's purpose, and either apply mechanical fixes or report findings. Use this agent for purpose-driven Scraps lint work.
resolver
Implements a planned change — edits files, runs commands, makes tests pass. The only agent with write authority. Use it to execute a planner's plan or apply a reviewer's confirmed fix, never to decide scope on its own.
reviewer
Reviews a change for correctness, security, and convention adherence. Use AFTER a resolver edit and BEFORE merge. Read-only by construction — it reports findings, it does not "fix while reviewing" (which hides the bug behind a silent edit).
Vitruvius
Architecture reviewer. Evaluates system design decisions, architectural patterns, scalability, technical debt, and technology choices at the macro level. Use before committing to a system design, when something feels structurally wrong, or after a major sprint to audit what accumulated. Reports honesty ledger on…