navigation-policy

Define browser navigation allowlists and configure screenshot and DOM evidence capture.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured framework for managing browser-based automation, ensuring that visual proof collection and navigation remain within safe, defined boundaries.

Core Features & Use Cases

  • Capability Control: Define explicit allowlists for browser navigation to prevent unauthorized access.
  • Evidence Management: Configure specific connectors for capturing screenshots and DOM evidence during automated tasks.
  • Use Case: When building a web-scraping agent, use this Skill to restrict the agent to specific subdomains and ensure that only relevant UI elements are captured as evidence, preventing the accidental collection of sensitive data.

Quick Start

Use the navigation-policy skill to define the allowed navigation paths and evidence capture requirements for the current browser automation task.

Frequently Asked Questions about navigation-policy

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

FAQPage Schema
How do I restrict browser automation to specific subdomains during web scraping?

To restrict browser automation, define explicit allowlists for navigation paths to prevent unauthorized access. This capability control confines automated agents to specific subdomains and ensures only relevant UI elements are captured.

What is deterministic visual proof collection in automated testing?

Deterministic visual proof collection is the structured capture of screenshots and DOM evidence during automated browser workflows. It applies capability boundaries to ensure safe execution and produces consistent visual regression testing outputs.

Can I configure specific connectors for capturing DOM evidence in automated capture harnesses?

Yes, you can configure specific connectors for capturing screenshots and DOM evidence. The framework manages evidence collection strategies to ensure that automated capture harnesses only collect approved visual proof.

How do I prevent accidental collection of sensitive data during visual regression testing?

You prevent accidental sensitive data collection by applying navigation policies that restrict agents to allowed paths. Defining these explicit boundaries ensures that automated visual regression testing only captures relevant UI elements.

What is the best way to manage audit logging for browser-based workflows?

The best way to manage audit logging is implementing a structured navigation policy that enforces capability boundaries. This provides deterministic proof collection and satisfies compliance requirements for safe browser execution.

When should I not use allowlists for browser navigation control?

You should not use navigation allowlists when a browser automation task requires open-ended exploration across unrestricted domains. The framework is designed for controlled capability boundaries and deterministic visual proof collection, limiting free-form scraping.