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 code-exploregit 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/code-explore)<a href="https://agentmods.dev/skills/sd0xdev/sd0x-harness/code-explore"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/code-explore/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/code-explore"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/code-explore.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.00051 | $0.01149 |
| Opus 5.5 | $0.00020 | $0.00460 |
| Sonnet 5.5 | $0.00010 | $0.00230 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade A, and why
code-explore 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Explore Skill
Trigger
- Keywords: code explore, code investigation, research code, trace code, feature understanding, quick investigation, code exploration
When to Use
- Quickly understand how a feature works
- Trace execution paths / data flow
- Diagnose problem root causes
- No dual confirmation needed (no Codex cross-validation)
When NOT to Use
| Scenario | Alternative |
|---|---|
| Need dual confirmation | /code-investigate (Claude + Codex) |
| Git history tracking | /git-investigate |
| System verification | /feature-verify |
| Code review | /codex-review-fast |
Workflow
┌──────────────────────────────────────────────────────────┐
│ Phase 1: Locate Entry Point │
├──────────────────────────────────────────────────────────┤
│ 1. Grep keywords -> find related files │
│ 2. Identify entry points (Controller / Service / Provider) │
│ 3. Build file list │
└──────────────────────────────────────────────────────────┘
↓
┌──────────────────────────────────────────────────────────┐
│ Phase 2: Trace Path │
├──────────────────────────────────────────────────────────┤
│ 1. Start from entry point, Read │
│ 2. Identify dependencies -> continue tracing │
│ 3. Map call chain (A -> B -> C) │
└──────────────────────────────────────────────────────────┘
↓
┌──────────────────────────────────────────────────────────┐
│ Phase 3: Understand Logic │
├──────────────────────────────────────────────────────────┤
│ 1. What is the core logic? │
│ 2. How does data flow? │
│ 3. Error handling mechanisms? │
│ 4. Key decision points? │
└──────────────────────────────────────────────────────────┘
↓
┌──────────────────────────────────────────────────────────┐
│ Phase 4: Output Report │
├──────────────────────────────────────────────────────────┤
│ 1. Architecture overview (diagram / table) │
│ 2. Key files list │
│ 3. Execution flow │
│ 4. Findings / notes │
└──────────────────────────────────────────────────────────┘
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 · 164 lines · 51 tokens per session scan A 609ec947ef29
code-explore is a skill published in the GitHub repository sd0xdev/sd0x-harness (193 stars, last pushed 8d ago), licensed MIT. It adds 51 tokens to every session and 1,149 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-08-30.
Other skills, from other repositories
resolving-merge-conflicts
Use when a git merge or rebase reports conflicts and the operation is in progress.
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-apply-fixes
Internal Auto-Harness generator skill for QA fix cycles. Use only inside the Generator subagent when it is addressing named defects from QA or retest.
comet-hotfix
A quick workflow for fixing an existing bug in Comet, a tool that manages structured code changes. It moves through opening the change, building, checking, and archiving it.
comet-hotfix
Comet preset path: Bug fix / hotfix. Skip brainstorming, directly open → build → verify → archive. Applicable for behavior fixes, scenarios not involving new capability design.