Borrowing it
Nothing to install: this file belongs to unbound-force/gaze. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/unbound-force/gaze/main/.opencode/skills/pre-flight/SKILL.mdgit clone --depth 1 https://github.com/unbound-force/gazeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/unbound-force/gaze/pre-flight)<a href="https://agentmods.dev/skills/unbound-force/gaze/pre-flight"><img src="https://agentmods.dev/badge/skills/unbound-force/gaze/pre-flight.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00030 | $0.04465 |
| Opus 5 | $0.00015 | $0.02233 |
| Sonnet 5 | $0.00006 | $0.00893 |
| Haiku 4.5 | $0.00003 | $0.00447 |
Grade A, and why
pre-flight scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 552 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Pre-flight Checks
Shared logic for CI workflow detection, local tool detection, CI coverage matrix generation, and local tool execution. Consuming commands load this skill and select an execution policy.
Execution Policies
| Mode | Behavior | Typical consumer |
|---|---|---|
hard-gate |
Run all detected tools. Stop on first failure. | /unleash (phase checkpoints) |
ci-aware |
Build CI coverage matrix against PR check results. Skip tools CI already verified. Run the rest. | /review-pr |
soft-gate |
Run all detected tools. Classify failures as branch-caused vs pre-existing. Gate only on branch-caused failures. | /review-council |
The consuming command specifies which mode to use.
Phase 1: CI Workflow Parsing
Read all files in .github/workflows/ to identify the
exact commands CI runs. Do NOT hardcode language-specific
commands — the workflow files are the source of truth.
Extraction rules
- Extract only
run:step commands from workflow YAML. - Ignore
uses:steps — these are GitHub-hosted actions and are not locally executable. - Skip commands containing unresolvable CI expressions
(
${{ secrets.* }},${{ github.* }}) with a warning noting unresolvable CI expressions. These commands depend on CI runtime context and cannot run locally. - Multi-line
run:blocks: extract each command line individually. Skip lines that are pure shell control flow (if/then/fi, variable assignments used only within the block).
Output
A list of CI commands discovered from workflows, e.g.:
CI commands discovered from .github/workflows/:
- go build ./... (ci_local.yml)
- go test -race -count=1 -coverprofile=coverage.out ./... (ci_local.yml)
If no .github/workflows/ directory exists, report
"No CI workflows found" and proceed to Phase 2.
Phase 2: Local Tool Detection
Check which tools are available by looking for their configuration files:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 552 lines · 30 tokens per session scan A 301dc7df3767
pre-flight is a skill published in the GitHub repository unbound-force/gaze (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 30 tokens to every session and 4,465 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
migrate-vstest-to-mtp
Use this skill before answering, planning, or editing whenever .NET tests or CI are switching from VSTest to Microsoft.Testing.Platform (MTP), or an MTP migration behaves differently. Triggers include "switch from VSTest"; MSTest/NUnit/xUnit MTP enablement; OutputType=Exe only for test projects in…
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…
playwright-ci
Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.
ci-maintenance-workflow
CI and GitHub Actions maintenance workflows — fix a failing test from a CI URL, fix a failing smoke test, add @pytest.mark.slow markers to slow tests, or review a PR against agent-checkable standards. Use when user asks to fix a failing test, fix a smoke test, mark slow tests, or review a PR. Trigger when the user…
test-setup
Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.