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.
git clone --depth 1 https://github.com/HubWizard/second-passWrote 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/commands/hubwizard/second-pass/reset)<a href="https://agentmods.dev/commands/hubwizard/second-pass/reset"><img src="https://agentmods.dev/badge/commands/hubwizard/second-pass/reset/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/commands/hubwizard/second-pass/reset"><img src="https://agentmods.dev/badge/commands/hubwizard/second-pass/reset.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.00026 | $0.00230 |
| Opus 5.5 | $0.00010 | $0.00092 |
| Sonnet 5.5 | $0.00005 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
reset 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
Reset Second Pass settings to defaults
The user wants to reset all Second Pass settings to defaults.
Perform these steps:
-
Ensure the config directory exists:
~/.claude/second-pass/. Create it if missing. -
Overwrite
~/.claude/second-pass/config.jsonwith the default config (pretty-printed, 2-space indent):{ "passing_grade": "B", "iteration_cap": 3, "confirm_revisions": false }Do not merge with existing config — this command is a full reset.
-
Confirm to the user in a single line:
Second Pass settings reset. Bar: B. Cap: 3. Confirm revisions: off.
Do not ask for confirmation before overwriting. Do not explain what Second Pass is. Do not list alternative commands. This is a reset — be terse and done.
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 · 30 lines · 26 tokens per session scan A d3a5fdc6fec0
reset is a command published in the GitHub repository HubWizard/second-pass (2 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 230 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-08-31.
Other commands, from other repositories
pr
Take the current branch from uncommitted work to an open pull request: commit outstanding changes with the git-commit rules if asked, push with upstream tracking, write the PR title and body with the pr-description skill from the full branch diff, link the issue, and open it with gh against the right base. Confirms…
check
A combined code-quality review and design-to-implementation consistency check. It reads the changed files once, then evaluates them from both review perspectives.
design
A command that turns an existing plan into a detailed technical design for building the feature.
support-model
Write a support model as Markdown in the user's repository. Produce designed HTML or PDF only when asked.
design-doc
Write a design doc / RFC as Markdown in the user's repository. Use when invoked as /document-design-system:design-doc. Produce designed HTML or PDF only when asked.
evaluate
Execute Evaluate stage to validate generated framework artifacts.