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 wangke19/gemini-ai-helpers --skill coderabbit-inheritance-scanner-open-prgit clone --depth 1 https://github.com/wangke19/gemini-ai-helpersWrote 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/wangke19/gemini-ai-helpers/coderabbit-inheritance-scanner-open-pr)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/coderabbit-inheritance-scanner-open-pr"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/coderabbit-inheritance-scanner-open-pr/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/wangke19/gemini-ai-helpers/coderabbit-inheritance-scanner-open-pr"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/coderabbit-inheritance-scanner-open-pr.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.00031 | $0.01617 |
| Opus 5 | $0.00015 | $0.00809 |
| Sonnet 5 | $0.00006 | $0.00323 |
| Haiku 4.5 | $0.00003 | $0.00162 |
Grade C, and why
CodeRabbit Inheritance Scanner - Open PR scanned grade C with 1 finding 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 8d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf "${WORKDIR}" 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.
CodeRabbit Inheritance Scanner - Open PR
This skill handles the complete workflow of opening a pull request to add inheritance: true to a repository's .coderabbit.yaml file. It always operates via a personal fork to avoid needing direct push access to upstream repos.
When to Use This Skill
Use this skill as Step 6 of the /teams:coderabbit-inheritance-scanner command, after the user has confirmed they want to open PRs. Call it once per non-compliant repo that does not already have an open fix PR.
Do NOT call this skill in --dry-run mode. Instead, display the actions that would be taken for each repo.
Prerequisites
ghCLI authenticated withreposcopeworkflowscope is needed if the upstream repo contains GitHub Actions workflow files (forgh repo sync). If missing, the skill will skip the repo with a warning.
Procedure
For each repo that needs a fix PR, run the following. The variables REPO (e.g., openshift/api), DEFAULT_BRANCH (e.g., master or main), and CFGFILE (e.g., .coderabbit.yaml) must be set.
# Derive names
REPO_NAME="${REPO##*/}"
GH_USER=$(gh api user --jq '.login')
WORKDIR="/tmp/cr-fix-workdir/${REPO_NAME}"
BRANCH_NAME="add-coderabbit-inheritance"
echo "Processing: ${REPO}"
# Step 1: Fork the repo (idempotent - safe to call if fork exists)
gh repo fork "${REPO}" --clone=false 2>&1 || true
sleep 2
# Step 2: Sync the fork's default branch with upstream
SYNC_OUTPUT=$(gh repo sync "${GH_USER}/${REPO_NAME}" --source "${REPO}" --branch "${DEFAULT_BRANCH}" 2>&1)
SYNC_EXIT=$?
if [ $SYNC_EXIT -ne 0 ]; then
if echo "$SYNC_OUTPUT" | grep -q "workflow"; then
echo "SKIP|${REPO}|Fork sync failed: workflow scope required. Run: gh auth refresh -h github.com -s workflow"
# Continue to next repo in the calling loop
return 1 2>/dev/null || continue
fi
echo "SKIP|${REPO}|Fork sync failed: ${SYNC_OUTPUT}"
return 1 2>/dev/null || continue
fi
# Step 3: Delete any stale branch from a previous run
gh api -X DELETE "repos/${GH_USER}/${REPO_NAME}/git/refs/heads/${BRANCH_NAME}" 2>/dev/null || true
sleep 1
# Step 4: Clone the fork and create the fix branch
rm -rf "${WORKDIR}"
if ! gh repo clone "${GH_USER}/${REPO_NAME}" "${WORKDIR}" -- -b "${DEFAULT_BRANCH}" --depth 1 2>&1; then
echo "ERROR|${REPO}|Clone failed"
return 1 2>/dev/null || continue
fi
cd "${WORKDIR}" || { echo "ERROR|${REPO}|cd into workdir failed"; return 1 2>/dev/null || continue; }
git checkout -b "${BRANCH_NAME}" 2>&1 || { echo "ERROR|${REPO}|Branch creation failed"; cd /tmp; return 1 2>/dev/null || continue; }
# Step 5: Add inheritance: true to the config file
if [ ! -f "${CFGFILE}" ]; then
echo "ERROR|${REPO}|Config file ${CFGFILE} not found in cloned repo"
cd /tmp
return 1 2>/dev/null || continue
fi
if ! grep -qE '^\s*inheritance:\s*(true|false)\b' "${CFGFILE}"; then
# Prepend inheritance: true as the first line
printf 'inheritance: true\n' | cat - "${CFGFILE}" > "${CFGFILE}.tmp" && mv "${CFGFILE}.tmp" "${CFGFILE}"
else
# Replace existing inheritance: false with true
sed -i.bak 's/^\(\s*\)inheritance:\s*false/\1inheritance: true/' "${CFGFILE}" && rm -f "${CFGFILE}.bak"
fi
# Step 6: Commit and push
git add "${CFGFILE}"
git commit -m "$(cat <<'COMMITEOF'
Add inheritance: true to .coderabbit.yaml
Ensures this repo inherits the org-wide CodeRabbit review rules
defined in https://github.com/openshift/coderabbit
COMMITEOF
)" 2>&1
git push origin "${BRANCH_NAME}" 2>&1
# Step 7: Create the PR from fork to upstream
PR_URL=$(gh pr create \
--repo "${REPO}" \
--head "${GH_USER}:${BRANCH_NAME}" \
--base "${DEFAULT_BRANCH}" \
--title "Add CodeRabbit inheritance for org-wide rules" \
--body "$(cat <<'BODYEOF'
Adds `inheritance: true` to `.coderabbit.yaml` so this repo inherits the org-wide review rules from [openshift/coderabbit](https://github.com/openshift/coderabbit).
Without this setting, the repo's custom `.coderabbit.yaml` overrides the org-level configuration entirely, meaning org-wide review instructions and path-based rules are not applied.
BODYEOF
)" 2>&1)
cd /tmp
if echo "$PR_URL" | grep -q "https://github.com"; then
echo "OK|${REPO}|${PR_URL}"
else
echo "ERROR|${REPO}|PR creation failed: ${PR_URL}"
fi
sleep 1
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.
- 8d ago First seen · 149 lines · 0 tokens per session scan C e132f2a61e43
CodeRabbit Inheritance Scanner - Open PR is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 31 tokens to every session and 1,617 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
create-pr
Create pull requests following Sentry conventions. Use when opening PRs, writing PR descriptions, or preparing changes for review. Follows Sentry's code review guidelines.
codex-review
Professional code review with auto CHANGELOG generation, integrated with Codex AI.
pr-review-fix-pipeline
Autonomous PR review that also applies fixes for non-controversial issues — combines review, fix, test, and commit into a single pipeline. Unlike a read-only review, this writes code. Only use on feature branches where you're comfortable with automatic edits. Trigger on: "review and fix PR", "auto-fix the PR", "clean…
everything-claude-code-conventions
Core repository standards for naming, structure, commits, and workflows.
yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (gh).
comprehensive-review-pr-enhance
You are a PR optimization expert specializing in creating high-quality pull requests that facilitate efficient code reviews. Generate comprehensive PR descriptions, automate review processes, and ensure PRs follow best practices for clarity, size, and reviewability.