skills / role-bleed-probe
CLAUDE.md0 starsChanged 4 months agoMITView on GitHub
This is a runnable evaluation tool. Follow these steps to run the full probe end-to-end. - Python 3 (no third-party packages required). - At least one supported agentic CLI installed (e.g. grok, codex, agy for Gemini). Verify with which grok (or whichever model you intend to probe). - The CLI must be authenticated / have its API key configured. The probe does not manage credentials — set them via the CLI's own env var or config file before running. Expected…
In this repository19 other files it gives its agents.
- construct-validity-screen/CLAUDE.mdCLAUDE.md
- adversarial-hardenSkill
- ai-proofSkill
- construct-validity-screenSkill
- divergent-solveSkill
- forgeSkill
- gate-canariesSkill
- grill-meSkill
- heavy-task-plannerSkill
- overnightSkill
- parallel-researchSkill
- premise-gateSkill
- prompt-architectSkill
- role-bleed-probeSkill
- scope-firstSkill
- session-handoffSkill
- stakes-gateSkill
- voice-profileSkill
- witnessSkill
The file
We split this CLAUDE.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 9
Verify with which grok (or whichever model you intend to probe).
- Very specific: line 36
Use --n 15 or higher for a publishable rate.
≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
role-bleed-probe — Claude Code quick-start
This is a runnable evaluation tool. Follow these steps to run the full probe end-to-end.
Prerequisites
- Python 3 (no third-party packages required).
- At least one supported agentic CLI installed (e.g.
grok,codex,agyfor Gemini). Verify withwhich grok(or whichever model you intend to probe). - The CLI must be authenticated / have its API key configured. The probe does not manage credentials — set them via the CLI's own env var or config file before running.
Step 1 — Verify the scorer
python3 probe/score.py --self-testExpected output: self-test OK. If this fails, check that probe/markers.json is present.
Step 2 — Dry run (no tokens spent)
python3 probe/run_probe.py --models grokPrints the run plan and sample prompts. No model is called.
Step 3 — Single-shot paired probe
python3 probe/run_probe.py --yes --models grok --n 5Runs 5 replicates per condition pair. Results go to probe/results.jsonl.
Use --n 15 or higher for a publishable rate.
To run only the sustained-load condition (T5) with trace saving:
python3 probe/run_probe.py --yes --models grok --only T5 --turns 40 --save-tracesStep 4 — Multi-turn faithful reproduction
python3 probe/run_multiturn.py --model grok # dry run first
python3 probe/run_multiturn.py --yes --model grok --n 5 # real runResults go to probe/mt_results.jsonl. Requires grok (or another adapter with
multiturn_capable: true and continue_cmd set in probe/adapters.json).
Step 5 — Score an existing trace
python3 probe/score.py path/to/trace.txt
# or via stdin:
python3 probe/score.py < trace.txtStep 6 — Re-aggregate an existing run
python3 probe/run_probe.py --summarize probe/results.jsonl
python3 probe/run_multiturn.py --summarize probe/mt_results.jsonlKey outputs to read
leaked: did any marker fire in the reasoning text?fired: which markers?self_naming_3pis the headline signal.rc: agent exit code — always report task outcome alongside leak rate.reasoning_chars: sanity-check that you captured the reasoning channel (not just a final answer).- Within-pair delta in the summary table: treatment − control leak points. This is the strong, unconfounded result.
Adding a new model
Edit probe/adapters.json: add an entry with cmd, reasoning, model_name, enabled: true.
For multi-turn, also add continue_cmd and multiturn_capable: true. Then re-run steps 1–2.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

