scan-scheduler

Adjust scope-scan frequency and ontology rebuild strategies to control compute costs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses excessive compute waste and token consumption by providing a structured framework to tune scan frequencies and rebuild strategies within the Project Scope harness.

Core Features & Use Cases

  • Cost Control: Adjusts scope-scan frequency to prevent unnecessary recompute cycles.
  • Ontology Management: Switches between incremental and full ontology rebuilds to balance accuracy with resource efficiency.
  • Use Case: When a project's dependency graph becomes too large, use this skill to shift from full rebuilds to incremental updates, significantly reducing token usage and latency.

Quick Start

Initiate the scan-scheduler process by identifying the current Project Scope boundary and selecting a specific lever to reduce compute waste.

Frequently Asked Questions about scan-scheduler

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

FAQPage Schema
How do I reduce token usage and compute costs for scope-scan frequency?

To reduce compute costs and token usage, you can tune scope-scan frequency to prevent unnecessary recompute cycles. This directly optimizes project resource consumption by limiting redundant scans within the project boundary.

What is the best way to manage ontology rebuilds for a large dependency graph?

Managing ontology rebuilds involves switching between incremental and full rebuilds. For large dependency graphs, shifting to incremental updates significantly reduces token usage and latency while balancing structural accuracy with resource efficiency.

Do I need observability logs to optimize project scope and control compute costs?

Yes, optimizing project scope requires access to observability logs. These logs are necessary to verify the impact of control changes on resource consumption and ensure the compute cost adjustments are effectively bounded.

When should I switch from full ontology rebuilds to incremental updates?

You should switch from full ontology rebuilds to incremental updates when a project's dependency graph becomes too large. This shift balances accuracy with resource efficiency, significantly cutting down token usage and latency.

How does scan-scheduler handle excessive compute waste in software engineering workflows?

Scan-scheduler handles excessive compute waste by providing a structured framework to tune scan frequencies and rebuild strategies. It applies to software engineering workflows where token usage, storage, and compute costs must be strictly bounded.