Docs

Scanner quickstart and hosted onboarding in one place.

Run the free CLI scanner for local discovery and basic findings, then move into hosted DirectiveOps when you are ready for repo inventory, shared standards, and rollout control.

Use this page for scanner commands, export options, and hosted setup steps. For more context, see Product and Pricing.

Quick start

Try the scanner locally

CLI scanner commands

# Clone the OSS scanner repo

$git clone https://github.com/pithpusher/DirectiveOps-Scanner.git && cd DirectiveOps-Scanner

# Install and scan

$npm install && npx directiveops-scanner scan --path /your/repo

# Export findings

$npx directiveops-scanner scan --path /your/repo --format json --output report.json --markdown report.md

From inside a repo, use --path . to scan the current directory.

Need fleet-wide standards and rollout? See pricing →

View on GitHub Supported file types

Hosted product

Move from local scans to hosted standards and rollout.

Sign in with GitHub, choose a plan, install the GitHub App on your org, select repositories, and sync. The dashboard surfaces repo inventory, drift findings, templates, and rollout controls. For a deeper walkthrough of the hosted dashboard, see the Product page.

1Sign in with GitHub

2Choose a plan and install the GitHub App

3Select repos, sync, and review findings

Start setup Try the demo

How directives stack

Precedence across files and paths

Agents read multiple instruction surfaces in a single repo: repository-wide files such as AGENTS.md, CLAUDE.md, or .github/copilot-instructions.md, path-scoped .github/instructions/*.instructions.md, and tool-specific layers such as AGENTS.override.md where tools support overrides. Effective behavior is the merge of those layers—not whichever file was edited last in Git.

DirectiveOps models each discovered file with a precedence score derived from file type and path (for example, scoped instructions under .github/instructions/ rank above repo-wide defaults). The instruction viewer and constitution graph show which layers contribute directives so operators can answer "what is the agent effectively following here?"

Vendor tools differ in merge rules; DirectiveOps does not execute agents. Treat the dashboard as a reviewable mapof repo-resident directives, then validate critical behavior against each vendor's documentation for Codex, Copilot, Claude Code, or Gemini CLI.

Supported instruction file types

Reports

Instruction sprawl, summarized for sharing

Scanner output gives you a quick, shareable view of instruction sprawl: how many files you have, how many directives they contain, and where drift or conflicts show up across a repo.

To share findings without exposing repo names or file paths, run the scanner with --markdown report.md --sanitize. The Markdown report keeps counts and finding types only and adds a small "Powered by DirectiveOps scanner" footer so others can reproduce the scan.

When you are ready to move beyond a single repo, upload the JSON report on onboarding to preview the summary, then connect GitHub to sync repos and manage standards from the hosted dashboard.

More detail

Go deeper on security, packaging, and rollout

GitHub App and security

Least-privilege permissions, verified webhooks, and branch-aware sync.

Open-core packaging

Scanner stays local and free. Hosted plans add standards, rollout, and history.

Constitution model

Files are parsed into layers, directives, and precedence rules.

Rollout engine

Preview changes, generate PRs, and track acceptance across repos.