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 simplifygit 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/simplify)<a href="https://agentmods.dev/skills/sd0xdev/sd0x-harness/simplify"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/simplify/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/simplify"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/simplify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium MCP Rug Pull · line 4 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00016 | $0.00380 |
| Opus 5.5 | $0.00006 | $0.00152 |
| Sonnet 5.5 | $0.00003 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
simplify 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.
What it actually says
Code Simplification
Trigger
- Keywords: simplify, clean up code, remove duplication, simplify code
When NOT to Use
- New feature development (use
/feature-dev) - Document refactoring (use
/doc-refactor) - Full multi-target refactoring (use
/refactor)
Agent Dispatch
Primary: Code Simplification
Agent({
description: "Simplify code, eliminate duplication, preserve behavior",
subagent_type: "code-simplifier",
prompt: `Simplify the code at: $ARGUMENTS
Follow the task steps and constraints defined in this skill.`
})
Secondary: Refactoring Risk Review
After simplification, dispatch risk assessment:
Agent({
description: "Review refactoring risk and verify behavior preservation",
subagent_type: "refactor-reviewer",
prompt: `Review the refactoring changes just applied.
Check behavior preservation, dependency impact, test coverage, and rollback risk.`
})
Task
For $ARGUMENTS:
- Run tests first (establish baseline)
- Refactor
- Dead code removal
- Extract duplicates (3+ repeats)
- Simplify nesting (> 3 levels)
- Run tests again (confirm nothing broken)
Output
## Refactoring Summary
- [file:line] <change>
## Test Results
✅/❌
## Next Steps
- <suggestions>
Constraints
- ❌ Do not change business logic
- ❌ Do not add new features
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 · 76 lines · 16 tokens per session scan A 9562bed1330a
simplify is a skill published in the GitHub repository sd0xdev/sd0x-harness (194 stars, last pushed 14d ago), licensed MIT. It adds 16 tokens to every session and 380 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-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.
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.