git404hub

what is rulesentry fr?

mohamedzhioua/rulesentry — explained in plain English

Analysis updated 2026-05-18

2TypeScriptAudience · developerComplexity · 2/5Setup · easy

tl;dr

A scanner that finds hidden malicious instructions embedded in AI coding assistant configuration files like CLAUDE.md or .cursorrules. It detects invisible text, text-reordering tricks, and lookalike characters.

vibe map

mindmap
  root((rulesentry))
    What it does
      Finds hidden instructions
      Shows reveal diff
      Normalizes invisible chars
    Attacks detected
      Invisible Unicode
      Trojan Source bidi
      Homoglyph spoofing
    Integrations
      GitHub Action
      Pre-commit hook
    Outputs
      JSON SARIF format
      Scan receipts
    Use cases
      CI security checks
      Manual repo audits

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

what do people make with this?

VIBE 1

Run a security scan on your repo to find hidden instructions in AI assistant config files.

VIBE 2

Add rulesentry to your CI pipeline to block malicious commits automatically.

VIBE 3

Preview safe fixes and strip invisible characters from your config files.

VIBE 4

Generate JSON or SARIF security reports for GitHub's Security tab.

what's the stack?

TypeScriptnpx

how it stacks up fr

mohamedzhioua/rulesentry4ssh1/mine-sweeperachawla19/intuitcode-extension
Stars222
LanguageTypeScriptTypeScriptTypeScript
Last pushed2026-01-31
MaintenanceMaintained
Setup difficultyeasymoderatemoderate
Complexity2/52/54/5
Audiencedevelopervibe coderdeveloper

Figures from each repo's GitHub metadata at analysis time.

how do i run it?

Difficulty · easy time til it works · 5min

No installation or configuration needed, run directly with npx rulesentry scan.

No license information was provided in the explanation.

in plain english

rulesentry is a tool that catches hidden instructions smuggled into configuration files used by AI coding assistants. These are files like CLAUDE.md, .cursorrules, or copilot-instructions.md that tell an AI agent how to behave. The problem it addresses is that a human reviewer sees one thing when reading these files, but the AI reads the raw underlying data, and attackers can exploit that gap by embedding invisible text. The attacks work through several tricks. Invisible Unicode characters can hide entire commands inside a line that looks innocent to a person. Bidirectional override characters, known as Trojan Source, reorder text so the line you read differs from what the agent reads. Some Claude Code skill files can run shell commands and insert the output before the model sees the file, which means a malicious instruction can execute before anyone notices. Homoglyphs, like a Cyrillic letter that looks like a Latin one, can spoof an allow-list entry. rulesentry detects all of these and shows you exactly what the agent reads versus what you see, with precise byte offsets. You can run it with no installation or configuration using npx rulesentry scan, and it will automatically find and check the relevant agent files in your repository. A clean scan prints one line and exits successfully. If it finds problems, it prints a reveal diff and exits with an error code, which makes it suitable for automated use in continuous integration. You can also run rulesentry fix to preview safe normalization, or add --write to strip invisible characters in place. It only removes characters where the fix is unambiguous, leaving homoglyphs and executable strings flagged for human review. The tool integrates as a GitHub Action or a pre-commit hook, so scans run automatically on pushes and pull requests. It can output results in JSON or SARIF format for GitHub's Security tab. Every scanned file gets a receipt with hashes representing what a human perceives and what the agent actually reads, so code review has a verifiable record when those two values differ. The full README is longer than what was shown.

prompts (copy fr)

prompt 1
How do I use rulesentry to scan my repository for hidden instructions in CLAUDE.md and .cursorrules files?
prompt 2
Help me set up rulesentry as a GitHub Action to automatically scan for invisible Unicode and Trojan Source attacks on every pull request.
prompt 3
Show me how to run rulesentry fix with the --write flag to safely strip invisible characters from my AI coding assistant config files.
prompt 4
How do I configure rulesentry to output SARIF format so results show up in my GitHub Security tab?

Frequently asked questions

what is rulesentry fr?

A scanner that finds hidden malicious instructions embedded in AI coding assistant configuration files like CLAUDE.md or .cursorrules. It detects invisible text, text-reordering tricks, and lookalike characters.

What language is rulesentry written in?

Mainly TypeScript. The stack also includes TypeScript, npx.

What license does rulesentry use?

No license information was provided in the explanation.

How hard is rulesentry to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is rulesentry for?

Mainly developer.

peek the repo → explain another one

This repo across BitVibe Labs

double-check against the repo, no cap.