Borrowing it
Nothing to install: this file belongs to openshift/lightspeed-agentic-operator. 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/openshift/lightspeed-agentic-operator/main/.cursor/skills/rebase-clean/SKILL.mdgit clone --depth 1 https://github.com/openshift/lightspeed-agentic-operatorWrote 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/openshift/lightspeed-agentic-operator/rebase-clean)<a href="https://agentmods.dev/skills/openshift/lightspeed-agentic-operator/rebase-clean"><img src="https://agentmods.dev/badge/skills/openshift/lightspeed-agentic-operator/rebase-clean/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/openshift/lightspeed-agentic-operator/rebase-clean"><img src="https://agentmods.dev/badge/skills/openshift/lightspeed-agentic-operator/rebase-clean.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 47 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00053 | $0.01156 |
| Opus 5.5 | $0.00021 | $0.00462 |
| Sonnet 5.5 | $0.00011 | $0.00231 |
| Haiku 4.5 | $0.00005 | $0.00116 |
Grade A, and why
rebase-clean 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 1mo 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Rebase Workflow
Use this workflow exactly for rebases in this repository.
Rules
- Do not create extra temporary branches unless the user explicitly asks.
- Do not make unrelated edits.
- Do not stop after analysis; finish rebase and validation.
- Keep output brief and operational.
- Never assume target branch names; detect current branch first.
- Use
go test ./... -count=1from the repo root (this repo has nomake testwrapper).
Step 0: Detect Branch Context
- Run
git branch --show-current. - Treat detected current branch as the candidate target branch.
- Ask user to confirm explicitly before proceeding:
I detected '<current-branch>' as the current branch. Should I rebase this branch?
- If user specified a target branch, verify it matches current branch; if not, stop and ask.
- Do not run reset/rebase commands until this confirmation is received.
- Before any reset/rebase command, restate:
- current branch
- target branch
- approved baseline ref and confirm when there is any mismatch or ambiguity.
Step 1: Restore Branch Baseline (Rerun Only)
Use this step only when a prior rebase attempt failed or introduced unwanted edits. For a first rebase attempt, skip this step and go directly to Step 2.
- Checkout target branch.
- Hard reset to the known backup/base commit the user approved.
- Fetch
upstream.
Command pattern:
git checkout <branch>
git reset --hard <backup-or-approved-base>
git fetch upstream
Step 2: Rebase Onto Main
Run:
git rebase upstream/main
If conflicts occur, resolve only the conflicted files. Do not add extra refactors.
Step 3: Conflict Resolution Policy
For each conflicted file:
- Start from one side (
oursortheirs) as a temporary base. - Apply only minimal compatibility changes required to compile and run tests on the new base branch.
- Keep behavior from the feature commit unless it is incompatible with upstream removals/renames.
- Resolve matching tests together with production code changes.
- Avoid opportunistic refactors during conflict resolution.
- Go module conflicts: If
go.modorgo.sumconflict, prefertheirs(upstream) and rungo mod tidyafter.
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.
- 1mo ago First seen · 149 lines · 53 tokens per session scan A 4d13f9d47861
rebase-clean is a skill published in the GitHub repository openshift/lightspeed-agentic-operator (15 stars, last pushed today), licensed Apache-2.0. It adds 53 tokens to every session and 1,156 once invoked, about $0.0002 per session on Opus 5.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
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
pi-sync
Daily upstream-sync job for the pi Go port — fetch upstream pi, triage every change since the recorded pin, port what's in scope, verify idiomatic + parity via independent reviews, update the ledger, and push. Use for "sync with upstream", "porting job", or as the scheduled daily run.
crawlkit
Maintain and release the crawlkit Go library, preserving downstream compatibility for gitcrawl, slacrawl, discrawl, and notcrawl.
pyo3-bindings
PyO3 conventions for exposing a Rust core to Python: pyclass/pymethods, PyErr/PyResult error mapping, GIL release, properties, maturin builds, and pytest. Load when generating or reviewing PyO3 Python bindings for a Rust library.
pixiv-cli-develop
Implement, diagnose, refactor, and design Go changes in pixiv-cli. Use before source changes or engineering design; follow the coding handbook and the relevant architecture, test, MCP, native, or documentation workflow.
python-format
Formats Python files with ruff format and reports which files changed.