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 Jerry0022/dotclaude --skill tune-hardengit clone --depth 1 https://github.com/Jerry0022/dotclaudeWrote 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/jerry0022/dotclaude/tune-harden)<a href="https://agentmods.dev/skills/jerry0022/dotclaude/tune-harden"><img src="https://agentmods.dev/badge/skills/jerry0022/dotclaude/tune-harden/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/jerry0022/dotclaude/tune-harden"><img src="https://agentmods.dev/badge/skills/jerry0022/dotclaude/tune-harden.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Agent Snooping · line 55 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 56 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00147 | $0.04224 |
| Opus 5 | $0.00073 | $0.02112 |
| Sonnet 5 | $0.00029 | $0.00845 |
| Haiku 4.5 | $0.00015 | $0.00422 |
Grade A, and why
tune-harden 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 10d 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 — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tune Harden — Stabilization Pass
Harden the codebase: tests, bugs, architecture, and consistency — without
restructuring the UI. Scope: $ARGUMENTS.
Invocation Context
This skill can be invoked in three ways:
- Direct — user types
/tune-hardenor trigger phrase. Full skill runs as documented below. Asks questions when$AUTONOMOUS=0. - From
/run-agents— orchestrator detected a harden-style request. Perdeep-knowledge/agent-orchestration.md§ Single-Agent Shortcut, the orchestrator delegates directly to this skill (no wave model, no sub-branching). Pass--invoked-by=agents. - From
/run-autonomous— autonomous skill primed permissions, confirmed the user, and now delegates a harden task. Pass--invoked-by=autonomous(which implies--autonomous).
When --invoked-by is set, the skill adjusts:
- No qa-agent re-spawn if the parent already runs a qa wave/agent. Rely on the parent's qa result, request a focused re-test only after fixes.
- No redteam re-spawn if the parent has a redteam wave planned. Skip Step 9 redteam, flag for parent's wave instead.
- No permission priming assumed — parent handled it.
- AskUserQuestion suppressed (autonomous implied) when parent is
autonomous; when parent isagents, respect the parent's interactive/background mode.
The parent passes its mode via an additional flag when needed:
--parent-mode=background or --parent-mode=interactive.
Step 0 — Load Extensions
Check for optional overrides. Use Glob to verify each path exists before reading. Skip missing files silently.
- Global:
~/.claude/skills/tune-harden/SKILL.md+reference.md - Project:
{project}/.claude/skills/tune-harden/SKILL.md+reference.md - Merge order: project > global > plugin defaults
Project extensions can add framework-specific consistency rules (e.g. design token catalog, allowed spacing values, brand colors).
Step 1 — Parse Arguments
Scan $ARGUMENTS for:
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.
- 10d ago First seen · 352 lines · 147 tokens per session scan A d48e7ffe145a
tune-harden is a skill published in the GitHub repository Jerry0022/dotclaude (5 stars, last pushed yesterday), licensed MIT. It adds 147 tokens to every session and 4,224 once invoked, about $0.0007 per session on Opus 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-31.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
adversarial-reviewer
Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.
work
Deliver one maintainer-approved EmDash issue, choosing the bug-fix path for a defect and the direct implementation path for an enhancement or task.