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 skills add chf3198/copilot-governance --skill web-regression-governancegit 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/web-regression-governance)<a href="https://agentmods.dev/skills/chf3198/copilot-governance/web-regression-governance"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/web-regression-governance/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/chf3198/copilot-governance/web-regression-governance"><img src="https://agentmods.dev/badge/skills/chf3198/copilot-governance/web-regression-governance.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00780 |
| Opus 5 | $0.00017 | $0.00390 |
| Sonnet 5 | $0.00007 | $0.00156 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
web-regression-governance 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 9d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Regression Governance
Purpose
Establish enforceable regression protection for repositories where user-visible behavior is driven by HTML/CSS/JS (including runtime injection/DOM mutation patterns).
This skill defines controls that must block merges/releases when homepage or critical-route invariants regress.
Applicability
Use for:
website-staticrepositories.web-apprepositories with SSR/SPA routes where visual ordering and runtime rendering matter.- Any repo with HTML/CSS and route-specific runtime scripts that can mutate layout/visibility.
Core controls (required)
-
Fail-fast publish/runtime verification
- Runtime verification scripts must exit non-zero on invariant failures.
- No warning-only mode for release-critical checks.
-
Critical-route invariants
- Define route-specific assertions for primary pages (at minimum homepage + key conversion route).
- Assert hero/headline/primary CTA presence where applicable.
- Assert section-order constraints for above-the-fold safety.
-
Runtime mutation guardrails
- Route-targeted scripts must be explicitly scoped to intended routes.
- Add static checks that fail if scripts target forbidden routes (for example homepage mutations by service-page overrides).
-
Visual/DOM regression gate in CI
- Run objective visual/DOM checks in CI for pull requests and merge-group paths.
- Treat failures as blocking under strict profile.
-
Non-bypass governance wiring
- Required checks must be wired so merges cannot proceed when regression gates fail.
- Merge queue readiness must include regression gates.
-
Evidence and provenance
- Record before/after evidence (screenshots and assertion output) for critical routes.
- Keep release notes linked to exact check runs for traceability.
Verification matrix
For each change touching HTML/CSS/runtime JS or publish scripts, require:
- Static invariant checks: route-scope and forbidden-pattern detection.
- Runtime assertions: presence/order/visibility checks on critical routes.
- Visual/DOM assertions: deterministic checks in CI.
- Release verification: final post-publish verification must hard-fail on drift.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 98 lines · 34 tokens per session scan A 47fdd51c0ce7
web-regression-governance is a skill published in the GitHub repository chf3198/copilot-governance (1 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 780 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
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
compiler-port
Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.
verify
Build, launch, drive, and screenshot the OpenNOW Electron settings UI on Windows.
break
Renders a component you choose in every state and scenario on a temporary page and stress tests it.
visual-qa
MUST USE after building/changing any UI or when asked whether a page, component, or TUI looks right. Rigorous visual QA across web/page and terminal UIs. Prefer browser:control-in-app-browser for unauthenticated browser/page QA in Codex, then Playwright/agent-browser/dev-browser. Captures screenshot/TUI evidence with…
sprite-gen
Generate clean 2D game sprites and animation atlases with a component-row pipeline: base identity, numeric sprite-request SSoT, per-state layout guides, image-gen row strips, chroma-key alpha cleanup, connected-component frame extraction, cell-based atlas composition, QA reports, and runtime manifest framelayout. Its…