Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/chf3198/copilot-governance/openclaw-availability-utilizationnpx skills add chf3198/copilot-governance --skill openclaw-availability-utilizationgit clone --depth 1 https://github.com/chf3198/copilot-governanceWrote 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/chf3198/copilot-governance/openclaw-availability-utilization)<a href="https://agentmods.dev/skills/chf3198/copilot-governance/openclaw-availability-utilization"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/openclaw-availability-utilization.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 | $0.00032 | $0.00692 |
| Opus 5 | $0.00016 | $0.00346 |
| Sonnet 5 | $0.00006 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
openclaw-availability-utilization 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 4d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenClaw Availability + Utilization Ops
Purpose
Make OpenClaw usage operational by default instead of optional:
- Keep gateway reachable and healthy.
- Route heavy work to the best machine automatically.
- Enforce utilization targets so local-only execution does not drift.
Mandatory Session Preflight
Run before implementation sessions and every 60–90 minutes during long sessions.
- Network lane check
- Auto-detect fleet via
fleet-config.js profile. - If profile is
solo, skip fleet checks — use cloud fallback chain.
- Auto-detect fleet via
- Gateway health check
- Confirm OpenClaw service is up and model status responds.
- Provider budget check
- Confirm OpenRouter daily limits and remaining quota.
- Failover integrity check
- Confirm primary + fallback chains are still free-only and ordered.
Utilization Policy
Task routing matrix
- Heavy tasks (multi-suite Playwright runs, broad static analysis, large refactors): run through OpenClaw on Windows.
- Medium tasks (single feature + focused tests): split by pressure; prefer OpenClaw if Chromebook memory is constrained.
- Light tasks (small docs edits, tiny patches): local execution acceptable.
Minimum target utilization
For coding sessions longer than 45 minutes when fleet is available (profile=full or degraded):
- Prefer fleet lane for heavy workloads when reachable.
- If fleet is unavailable (profile=solo), use cloud free tier (Groq/Cerebras/OpenRouter).
- No fixed percentage mandate — use fleet when it adds value, skip when it doesn't.
Recovery Playbook
If availability drops:
- Re-check Tailscale status and SSH path.
- Re-validate OpenClaw health and model probe.
- Rotate to next free fallback chain if current model is degraded.
- If lane remains unstable, run local with explicit degraded-mode note and retry OpenClaw lane at next checkpoint.
Session Control Loop
Use this loop:
PRECHECK -> EXECUTE -> VERIFY -> UTILIZATION CHECK -> ADAPT
- PRECHECK: run mandatory preflight.
- EXECUTE: route work per matrix.
- VERIFY: run task tests/lint checks.
- UTILIZATION CHECK: compare actual OpenClaw usage vs target.
- ADAPT: re-route next slice if target missed.
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.
- 4d ago First seen · 81 lines · 32 tokens per session scan A 43af8142b874
openclaw-availability-utilization is a skill published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 692 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…