Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vibeic/vibe-icnpx agentmods add skills/vibeic/vibe-ic/regression-manageWrote 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/vibeic/vibe-ic/regression-manage)<a href="https://agentmods.dev/skills/vibeic/vibe-ic/regression-manage"><img src="https://agentmods.dev/badge/skills/vibeic/vibe-ic/regression-manage/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/vibeic/vibe-ic/regression-manage"><img src="https://agentmods.dev/badge/skills/vibeic/vibe-ic/regression-manage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.01309 |
| Opus 5 | $0.00036 | $0.00655 |
| Sonnet 5 | $0.00014 | $0.00262 |
| Haiku 4.5 | $0.00007 | $0.00131 |
Grade A, and why
regression-manage 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 6d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Regression Manage
Doctrine (v0.1.50): 把修法寫進工具，而非寫進 prompt. Programs first; AI is the backstop for owner-assignment narrative.
Once verification, synthesis, P&R, and signoff are scripted, the next bottleneck is keeping the regression green. This skill triages nightly / CI results and routes failures to the right skill / owner.
Mandatory Deterministic Preflight
# Validate every incoming regression-failure issue has fixture data:
python3 plugins/vibe-ic/programs/regression_issue_intake_check.py \
--issue <issue.json> --strict
The intake gate rejects issues without a verbatim repro snippet, expected output, or drop-in fixture — exactly the pattern that preceded the historical #5 thrashing loop. Do not start triage on an issue that fails intake. Refuse to "diagnose by reading the log" without the program's PASS.
When to use
- After each nightly regression completes
- When a critical failure appears mid-day
- When flaky tests are slowing down the team
- Weekly regression health review
Inputs
- Regression run log / database (Jenkins, LSF, Slurm, GitHub Actions)
- Known-failure list with owners
- Severity policy (tape-out blocker vs warning vs info)
- Branch / tag under test
Workflow
The five mechanical steps are deterministic and are now programs,
not prose. Run them in order; each emits a JSON report (--json <out>):
- Aggregate results (pass/fail/error/timeout per job, pass %, trend,
P0 count) — enforced by
programs/regression_report_aggregate.py. - Deduplicate (normalize-and-hash the failure signature so identical
failures collapse to one issue) — enforced by
programs/regression_failure_dedup.py. - Classify severity (P0 was-green-now-red on protected/release;
P1 new failure on feature branch; P2 flaky passes-on-retry;
P3 environmental license/disk/network) — enforced by
programs/regression_severity_classify.py. - Auto-triage (failing-step → target skill: timing→
/sta-review, DRC→/drc-fix, functional→/rtl-repair, formal→/formal-verify, …) — enforced byprograms/regression_failure_route.py. - Flaky-test quarantine (pass-on-retry AND fail → quarantine + open
ticket so flakes don't hide real regressions) — enforced by
programs/regression_flaky_quarantine.py.
What ships with it
2 files 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.
- 6d ago First seen · 124 lines · 72 tokens per session scan A 59af2f3ee491
regression-manage is a skill published in the GitHub repository vibeic/vibe-ic (23 stars, last pushed today), licensed Apache-2.0. It adds 72 tokens to every session and 1,309 once invoked, about $0.0004 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
analog-verify
Pre-simulation review and Spectre simulation verification for analog circuits. Reviews circuit netlist and testbench, runs simulation, produces margin report. Use after analog-design completes a netlist.
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…
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…
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.
playwright-testing
E2E testing with Playwright - Page Objects, cross-browser, CI/CD.
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…