diff-scanner

Limit secret and permission scans to changed surfaces with precompiled rule sets.

Updated May 11, 2026
One-click install
npx skills add https://github.com/AesopScott/mojo --skill diff-scanner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diff-scanner
Source: https://github.com/AesopScott/mojo/tree/main/harnesses/skills/diff-scanner
Command: npx skills add https://github.com/AesopScott/mojo --skill diff-scanner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses performance bottlenecks in the Guardrails harness by limiting security and permission scans to only the surfaces that have actually changed.

Core Features & Use Cases

  • Targeted Scanning: Restricts secret and permission scans to changed files, significantly reducing latency.
  • Rule Precompilation: Optimizes gate evaluation by pre-processing rule sets for faster execution.
  • Use Case: When updating a complex policy, use this Skill to ensure that only the modified configuration is validated, preventing unnecessary full-system scans that block throughput.

Quick Start

Run the diff-scanner skill to analyze the current Guardrails harness and identify the smallest possible scope for your performance optimization.

Frequently Asked Questions about diff-scanner

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

FAQPage Schema
How do I optimize Guardrails scan performance for large policy updates?

To optimize Guardrails scan performance, limit security and permission scans to only the changed configuration surfaces, preventing unnecessary full-system scans that block throughput. Targeted scanning restricts evaluation to modified files, significantly reducing latency.

Why does my full-system secret scan block CI throughput?

Full-system secret scans block throughput because they evaluate every file regardless of changes. Restricting scans to changed surfaces limits evaluation to modified files, significantly reducing latency and preventing unnecessary full-system scans.

Can I precompile rule sets for faster gate evaluation in Guardrails?

Yes, you can precompile rule sets to optimize gate evaluation in Guardrails. Rule precompilation pre-processes rule sets for faster execution, maintaining high-speed gate evaluation while applying safe, tested patches.

How do I limit permission scans to changed files in a Guardrails harness?

You limit permission scans to changed files by identifying the specific bottleneck and chosen control lever to implement a safe patch. Targeted scanning restricts secret and permission scans to changed surfaces, significantly reducing latency.

Do I need to identify specific bottlenecks before optimizing scan latency?

Yes, you need precise identification of the boundary, the specific bottleneck, and the chosen control lever to implement a safe, tested patch. This targeted approach limits scans to changed surfaces and precompiles rule sets for high-speed gate evaluation.