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/paultyng/skill-issuenpx agentmods add skills/paultyng/skill-issue/bisectWrote 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/paultyng/skill-issue/bisect)<a href="https://agentmods.dev/skills/paultyng/skill-issue/bisect"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/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/paultyng/skill-issue/bisect"><img src="https://agentmods.dev/badge/skills/paultyng/skill-issue/bisect.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.00121 | $0.02248 |
| Opus 5.5 | $0.00048 | $0.00899 |
| Sonnet 5.5 | $0.00024 | $0.00450 |
| Haiku 4.5 | $0.00012 | $0.00225 |
Grade A, and why
bisect scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
go run ./cmd/server & PID=$!; sleep 1; curl -fsS localhost:8080/health; kill $PID How it starts
The opening of the file, as written. The whole thing — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bisect
Drive git bisect to isolate the first commit that introduced a bug, then report it. The skill stops at the report. Fixing belongs to the user with full context.
When to use
- User asks to "bisect", "find the commit that broke X", says "this used to work", or names a regression in a specific test/build target.
ci-debug-loopexhausted log analysis without identifying a clear cause.- A behavior, test, or build that was green at a known earlier point is now red.
Do not use when the bug is obviously in the most recent commit (inspect it), or when the reproducer is too fragile/flaky to drive an automated bisect (fix the flake first).
Inputs (confirm before starting)
Per confirm-before-implementing, gather these before touching git bisect:
- Symptom: one-line description of what's broken (e.g. "TestExchangeToken fails with
unauthorized"). - Reproducer: a shell command that exits 0 when the bug is absent, 1 when present. If the user can't supply one, build it together (see Reproducer strategy).
- Known-bad ref: default
HEAD. - Known-good ref: default oldest commit within the last 2 weeks:
If the user has a tag, branch, or specific date in mind, use it instead.git rev-list --since='2 weeks ago' --reverse HEAD | head -1
Reproducer strategy
The reproducer must work at every commit in the bisect range. The reproducer that exists today often won't: APIs change, test files don't yet exist on old commits, etc. Pick the highest-applicable strategy:
- External reproducer (preferred). A self-contained shell script in
$TMPDIR(e.g./tmp/repro.sh) that builds and exercises the project from outside the source tree. Hits a stable surface (CLI flag, HTTP endpoint, exported function with stable signature) that survived the bisect range. Examples:
This survives any in-tree changes because the reproducer doesn't live in the tree.# CLI: build and check observable behavior go build -o /tmp/foo ./cmd/foo && /tmp/foo --some-flag | grep -q expected # HTTP: spin up server, hit endpoint, kill go run ./cmd/server & PID=$!; sleep 1; curl -fsS localhost:8080/health; kill $PID
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 · 154 lines · 121 tokens per session scan A a81227e67424
bisect is a skill published in the GitHub repository paultyng/skill-issue (8 stars, last pushed yesterday), licensed MIT. It adds 121 tokens to every session and 2,248 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
fix-merge-conflicts
Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution.
ray-skill
This skill integrates Spatie's Ray with the AI agent using curl to interact with the Ray MCP. It prioritizes a fast, tool-independent debugging loop.
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.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
fix
Debug and fix a reported defect, such as a failing build or tests, runtime or console errors, regressions, merge conflicts, red PR checks. Triggers "fix", "broken", "not working", "merge conflict", "fix CI".
what-broke
Use when an AI agent needs to stop guessing, find which version broke an app, compare releases, read git tags/diffs/changelogs, and connect the code change to provider context such as database, storage, deployment, and external runtime behavior before editing.