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 bisectgit 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/bisect)<a href="https://agentmods.dev/skills/drn/dots/bisect"><img src="https://agentmods.dev/badge/skills/drn/dots/bisect/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/bisect"><img src="https://agentmods.dev/badge/skills/drn/dots/bisect.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.00028 | $0.01038 |
| Opus 5.5 | $0.00011 | $0.00415 |
| Sonnet 5.5 | $0.00006 | $0.00208 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
bisect 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Bisect
Find the exact commit that introduced a bug using binary search with automatic test verification.
Arguments
$ARGUMENTS- Required: a test command to verify the bug (e.g., "go test ./pkg/..." or "npm test"), or a description of the bug to investigate manually
Context
- Current branch: !
git branch --show-current - Git status: !
git status --short - Recent commits (50): !
git log --oneline -50 2>/dev/null | head -50 - Test framework: !
find . -maxdepth 1 \( -name go.mod -o -name Gemfile -o -name package.json -o -name Cargo.toml -o -name pyproject.toml \) 2>/dev/null | head -5 - Latest tag: !
git describe --tags --abbrev=0 2>/dev/null | head -1
Instructions
Step 0: Validate state
- IF
git status --shortshows uncommitted changes, offer to stash them withgit stash push -m "bisect: stashing before bisect". If the user declines, stop and tell them to commit or stash first. - IF
$ARGUMENTSis empty, ask the user: "What test command should I run to detect the bug? Or describe the bug and I will check each commit manually."
Step 1: Determine boundaries
The "bad" commit is HEAD (current state where the bug exists).
For the "good" commit, ask the user or infer:
- IF the user provides a known-good commit or tag, use it.
- IF a latest tag exists, suggest it as the good commit: "Is the bug present in ? If not, I will use it as the good boundary."
- OTHERWISE, suggest a commit from the recent history (e.g., 20 commits back) and ask the user to confirm.
Step 2: Start bisect
git bisect start
git bisect bad HEAD
git bisect good <good-commit>
Report how many commits are in the range and the estimated number of steps (log2).
IF the range exceeds 1000 commits, warn the user: "This is a large range ( commits, ~ steps). Consider narrowing the boundaries."
Step 3: Run bisect
IF the user provided a test command:
- Use
git bisect run <test-command>for automatic bisection. - The test command should exit 0 for "good" (bug not present) and non-zero for "bad" (bug present).
- Monitor the output. IF the test command exits with 125 (skip), report that the commit could not be tested and bisect will skip it.
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 · 111 lines · 28 tokens per session scan A edebbf89d687
bisect is a skill published in the GitHub repository drn/dots (23 stars, last pushed 11d ago), licensed MIT. It adds 28 tokens to every session and 1,038 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
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
enable-check-includes-strict
Enable and migrate Chromium targets and directories to checkincludesstrict = true, diagnosing and resolving header include violations as part of the checkincludesstrict LSC. Use when adding directories to the allowlist, enabling strict header checks on targets, or resolving CHECKINCLUDESSTRICTUNTRIAGED targets.
resolve-handoff
Emit the complete Resolve handoff with exact modes, outcomes, test evidence, and publication state.
reproduce-and-fix-issues
Reproduce triaged Slack bugs through a configured app-control adapter, verify existing fixes, and open a bounded draft pull request only after before-and-after proof. Use only from the configured Benny repro automation.
comet-github-issue-fix
A workflow for fixing a confirmed Comet-related GitHub issue or review blocker within an isolated scope. It covers matching the work to the relevant workflow, testing the change, checking runtime results, and preparing a careful handoff.