integrity-scan
Skill22 starsChanged 6 months agoApache-2.0View on GitHub
Run the intelligence scanner to detect contradictions, drift, dead decisions, and missing cross-references across the entire memory workspace. Check current mode: cat memory/intel-state.json | python3 -c "import json,sys;print(json.load(sys.stdin)['governance_mode'])"
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- mind-mem-developmentSkill
- apply-proposalSkill
- memory-recallSkill
- mind-memSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 3
Run the intelligence scanner to detect contradictions, drift, dead decisions, and missing cross-references across the entire memory …
- Distinctive: line 6
After a session with significant decisions or changes
- Distinctive: line 8
When something "feels wrong" about the memory state
- Distinctive: line 9
Before making architectural decisions (verify no contradictions)
- Very specific: line 35
Check current mode: cat memory/intel-state.json | python3 -c "import json,sys;print(json.load(sys.stdin)['governance_mode'])"
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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
/scan — Memory Integrity Scan
Run the intelligence scanner to detect contradictions, drift, dead decisions, and missing cross-references across the entire memory workspace.
When to Use
- After a session with significant decisions or changes
- During weekly maintenance
- When something "feels wrong" about the memory state
- Before making architectural decisions (verify no contradictions)
How to Run
python3 maintenance/intel_scan.py "${MIND_MEM_WORKSPACE:-.}"What It Checks
- Contradictions — Decisions that conflict with each other (via ConstraintSignatures)
- Drift — Decisions referenced in daily logs but never formalized
- Dead decisions — Active decisions with no recent references
- Orphan tasks — Tasks referencing non-existent decisions
- Impact graph — Downstream effects of each decision
- Coverage — How many files are monitored vs total
Output
- Updates
intelligence/CONTRADICTIONS.md,intelligence/DRIFT.md,intelligence/IMPACT.md - Updates
memory/intel-state.jsonwith latest metrics and counters - Saves state snapshot in
intelligence/state/snapshots/ - Generates
intelligence/BRIEFINGS.mdweekly briefing
Modes
detect_only— Report issues, never propose changes (default)propose— Report issues AND generate fix proposals inintelligence/proposed/
Check current mode: cat memory/intel-state.json | python3 -c "import json,sys;print(json.load(sys.stdin)['governance_mode'])"
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.