rune-integrity-check

Scan persisted agent state files for prompt injection, memory poisoning, and tampering.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-integrity-check-dangvu008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rune-integrity-check
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-integrity-check
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-integrity-check-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI agents that read persisted state files (like .rune/ directories) are vulnerable to indirect prompt injection, memory poisoning, and identity spoofing. This Skill validates those files before they are loaded or merged, blocking adversarial content from hijacking agent behavior. ## Core Features & Use Cases - Prompt Injection Detection: Scans for zero-width Unicode characters, hidden instruction phrases, HTML comment payloads, and suspicious base64 strings in state files. - Identity Verification via Git-Blame: Checks commit authorship on .rune/ files to detect PR poisoning from external contributors. - Content Consistency Checks: Validates decision/convention entry formats, detects slopsquatted package names, and flags security-override conventions. - Use Case: Before a session-bridge loads .rune/decisions.md into context, run this Skill to confirm the file has not been tampered with, receiving a CLEAN, SUSPICIOUS, or TAINTED verdict. ## Quick Start Run an integrity scan on all files in the .rune/ directory and report any prompt injection or tampering findings.

Frequently Asked Questions about rune-integrity-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect prompt injection in agent state files?

Scan files for zero-width Unicode characters (U+200B-U+200F, U+FEFF), hidden instruction phrases like 'ignore previous' or '<SYSTEM>', HTML comments, and long base64 strings. Any match is recorded with file path, line number, and matched pattern.

What is memory poisoning in AI agent workflows?

Memory poisoning occurs when adversarial content is written into persisted agent state files (like .rune/decisions.md) that agents later read and act on. Integrity scanning before load detects injected instructions, tampered conventions, and slopsquatted package references.

How does git-blame help verify agent state file integrity?

Git-blame reveals the commit authorship history of .rune/ files. If an external or unexpected contributor modified state files in a PR, the file is flagged as SUSPICIOUS for human review, catching PR poisoning attempts.

What do CLEAN, SUSPICIOUS, and TAINTED verdicts mean?

CLEAN means no suspicious patterns were found across all scanned files. SUSPICIOUS indicates patterns that may suggest tampering and warrant human review. TAINTED means high-confidence adversarial content was detected and the file should be blocked.

Why scan for zero-width Unicode characters in markdown files?

Zero-width characters are invisible to human reviewers but readable by agents, making them the top vector for hidden instruction injection. The scan covers U+200B-U+200F, U+2028-U+202F, U+FEFF, and U+00AD ranges.

What happens if git is unavailable during the identity check?

The git-blame step is skipped and an INFO message 'git-blame unavailable, identity check skipped' is logged. The check never skips silently, so reviewers know identity verification did not occur.