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 drn/dots --skill rebasegit clone --depth 1 https://github.com/drn/dotsWrote 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/drn/dots/rebase)<a href="https://agentmods.dev/skills/drn/dots/rebase"><img src="https://agentmods.dev/badge/skills/drn/dots/rebase/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/drn/dots/rebase"><img src="https://agentmods.dev/badge/skills/drn/dots/rebase.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 76 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.00035 | $0.01245 |
| Opus 5.5 | $0.00014 | $0.00498 |
| Sonnet 5.5 | $0.00007 | $0.00249 |
| Haiku 4.5 | $0.00003 | $0.00125 |
Grade A, and why
rebase 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Current branch: !
git branch --show-current - Git status: !
git status --short - Remotes: !
git remote -v 2>/dev/null | head -10 - HEAD ref: !
git rev-parse --abbrev-ref HEAD 2>/dev/null | head -1 - Open PR: !
gh pr view --json number,url,headRefName 2>/dev/null | head -10 - Base ref: !
git branch -r 2>/dev/null | grep -oE 'origin/(main|master)' | head -1 - Commits vs main: !
git log origin/main..HEAD --oneline 2>/dev/null | head -20 - Commits vs master: !
git log origin/master..HEAD --oneline 2>/dev/null | head -20 - Arguments: $ARGUMENTS
Your task
Rebase the current branch onto the latest upstream default branch and force-push to update the remote PR branch.
Step 0: Validate state
- If HEAD is detached (not on a named branch), stop and tell the user: "Cannot rebase in detached HEAD state."
- Determine the current branch name.
Step 1: Determine the target remote
- Run
git remoteto list remotes. - If
upstreamexists, use upstream as the target remote. - Otherwise, use origin.
Step 2: Determine the default branch
If the user passed --onto <branch> in the arguments, use that branch as the rebase target instead of the default branch. Otherwise:
- Run
git symbolic-ref refs/remotes/<remote>/HEAD 2>/dev/null(where remote is from Step 1) and extract the branch name. - If that fails, check if
<remote>/mainexists withgit rev-parse --verify <remote>/main 2>/dev/null. - If that fails, check if
<remote>/masterexists withgit rev-parse --verify <remote>/master 2>/dev/null. - If none work, stop and tell the user: "Could not determine the default branch. Use --onto to specify."
If the current branch IS the default branch, stop and tell the user: "You are on the default branch. Rebase is not needed."
Step 3: Fetch
- Run
git fetch <remote> <default-branch>. - Report: "Fetching /..."
Step 4: Check if rebase is needed
- Run
git merge-base --is-ancestor <remote>/<default-branch> HEADto check if already up to date. - If the branch is already up to date (exit code 0 from the above), report "Already up to date with /." and skip to Step 6.
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 · 93 lines · 35 tokens per session scan A 84e59c6270bd
rebase is a skill published in the GitHub repository drn/dots (23 stars, last pushed 11d ago), licensed MIT. It adds 35 tokens to every session and 1,245 once invoked, about $0.0001 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-30.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…