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 sd0xdev/sd0x-harness --skill git-investigategit clone --depth 1 https://github.com/sd0xdev/sd0x-harnessWrote 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/sd0xdev/sd0x-harness/git-investigate)<a href="https://agentmods.dev/skills/sd0xdev/sd0x-harness/git-investigate"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/git-investigate/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/sd0xdev/sd0x-harness/git-investigate"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/git-investigate.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.00053 | $0.00547 |
| Opus 5.5 | $0.00021 | $0.00219 |
| Sonnet 5.5 | $0.00011 | $0.00109 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
git-investigate 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Investigate Skill
Trigger
- Keywords: code history, git blame, track changes, who wrote this, when was it changed, root cause, code archaeology
When NOT to Use
- Code review (use codex-review)
- Feature development (use feature-dev)
- Just want to read code (use Read directly)
Command
/git-investigate src/service/xxx.ts:123 # Specific line
/git-investigate processToken # Function name
/git-investigate "error message" # Keyword
Workflow
Locate code -> git blame -> find commit -> trace history -> analyze changes -> report
Investigation Framework
| Question | Method |
|---|---|
| Who wrote it? | git blame |
| When was it changed? | git log --follow |
| Why was it changed? | commit message + PR |
| What was missed? | git diff compare original vs problematic version |
Common Patterns
| Pattern | Symptom | Root Cause |
|---|---|---|
| Type removed | Enum value deleted | Assumed no longer needed |
| Condition simplified | If conditions reduced | Missed during refactoring |
| Rename | Partially unchanged | Incomplete search-and-replace |
| Boundary ignored | Only handles main flow | Edge cases not considered |
Output
## Git Investigation Report
- **Target**: <file/feature>
- **Timeline**: <commit range>
- **Root cause**: <analysis>
- **Introduced by**: <commit hash + author>
Verification
- Report includes: investigation target, author info, timeline, original vs problematic code
- Root cause has clear analysis
- Fix recommendation is specific and actionable
References
references/commands.md- Git command reference + report template
Examples
Input: Who changed this line of code?
Action: git blame -> find commit -> trace PR -> output report
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 82 lines · 53 tokens per session scan A c6c7bea9d22e
git-investigate is a skill published in the GitHub repository sd0xdev/sd0x-harness (194 stars, last pushed 13d ago), licensed MIT. It adds 53 tokens to every session and 547 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-09-03.
Other skills, from other repositories
resolving-merge-conflicts
Use when a git merge or rebase reports conflicts and the operation is in progress.
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.
update
Safe cc10x upgrade through the Claude Code plugin CLI. Lists every installed scope, refreshes the marketplace, updates each scope, and optionally carries local patches over to the new install. Use this skill when: updating cc10x, upgrading, pulling latest cc10x, syncing plugin, refreshing cache, or checking for new…
debugging
Use when diagnosing a defect or regression: feedback loop FIRST, root cause before fix, blast radius after fix. Covers the 10-rung construction ladder, LSP-powered tracing, hypothesis quality criteria, and four-phase investigation.
codebase-hygiene
Two-mode skill: (1) find semantic duplicates — functions doing the same thing under different names, invisible to copy-paste detectors; (2) deepen shallow modules — thin wrappers and pass-through layers that spread complexity. Advisory and read-only; changes route through BUILD with full gates.
generator-fix-integrator
Internal Auto-Harness generator skill for worktree-merge fix integration. Use only inside the parallel Generator integrator when it is addressing named defects from QA or retest.