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 human-avatar/skills-for-humanity --skill s4h-logic-fixergit clone --depth 1 https://github.com/human-avatar/skills-for-humanityWrote 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/human-avatar/skills-for-humanity/s4h-logic-fixer)<a href="https://agentmods.dev/skills/human-avatar/skills-for-humanity/s4h-logic-fixer"><img src="https://agentmods.dev/badge/skills/human-avatar/skills-for-humanity/s4h-logic-fixer/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/human-avatar/skills-for-humanity/s4h-logic-fixer"><img src="https://agentmods.dev/badge/skills/human-avatar/skills-for-humanity/s4h-logic-fixer.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.00137 | $0.01334 |
| Opus 5 | $0.00068 | $0.00667 |
| Sonnet 5 | $0.00027 | $0.00267 |
| Haiku 4.5 | $0.00014 | $0.00133 |
Grade A, and why
s4h-logic-fixer 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 9d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logic Fixer
Diagnosis without repair is incomplete. This skill takes broken reasoning and produces a corrected version — one where the premises actually support the conclusion, the hidden assumptions are made explicit, the fallacies are removed, and the argument can be defended.
The output is not a critique. It is a fixed version of what you were trying to say.
Your Process
Step 1: Diagnose before repairing Don't jump to a fix. First, be specific about what's broken:
- What type of failure is this? (Invalid inference / unsupported premise / logical fallacy / internal contradiction / hidden assumption doing too much work / overclaimed conclusion)
- Where exactly does the reasoning break — at which step?
- What is the argument trying to establish? (Separate the intent from the execution — the intent might be sound even if the argument isn't.)
Framing check: Confirm the argument being examined before continuing. State what you've identified — the actual argument being analyzed, the conclusion it is trying to establish, and the apparent failure type — in one sentence, then use AskUserQuestion:
- Question: "I'm reading this as: [your one-sentence framing of the argument, its intended conclusion, and what appears broken]. Is that right?"
- Header: "Framing"
- Options:
- Yes — proceed — framing is correct
- Adjust — one element is off; user will correct it before you continue
- Reframe — different situation than read; incorporate the correction before proceeding
Step 2: Classify the repair needed Different failure modes need different repairs:
| Failure | Repair |
|---|---|
| Unsupported premise | Add evidence, or qualify the premise |
| Overclaimed conclusion | Narrow the conclusion to what the premises actually support |
| Missing step | Make the implicit inference explicit |
| Circular reasoning | Identify the begged question; provide independent support for the conclusion |
| False dichotomy | Reframe to acknowledge the full option space |
| Invalid inference | Add the bridging premise that makes the inference valid |
| Equivocation | Disambiguate the term; use different words for different senses |
| Hidden assumption | Surface it as an explicit premise; assess whether it holds |
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.
- 9d ago First seen · 118 lines · 137 tokens per session scan A 2c1baac69712
s4h-logic-fixer is a skill published in the GitHub repository human-avatar/skills-for-humanity (223 stars, last pushed 1mo ago), licensed MIT. It adds 137 tokens to every session and 1,334 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-09-03.
Other skills, from other repositories
fishbone-diagram
Map causes of a problem across categories (People, Process, Technology, Environment, etc.) to find root drivers.
five-whys
Find root cause of a problem by asking "Why?" five times — moving from symptom to systemic cause.
release-it
Build production-ready systems with stability patterns: circuit breakers, bulkheads, timeouts, and retry logic. Use when the user mentions "production outage", "circuit breaker", "deployment pipeline", "chaos engineering", "retry storm", "health checks", "my service keeps crashing", "prevent cascading failures", or…
thinking-kepner-tregoe
Use when a selective defect needs IS/IS-NOT difference analysis or a consequential option choice needs must/want weighting and adverse-consequence comparison.
anti-patterns
Catalogue of known SDLC anti-patterns that greatcto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
windows-compat
Audit and harden this Rust repo (code-graph-mcp) for Windows correctness: path-spelling drift between producers, the 32,767-char command-line cap, index-key mismatches, and path predicates that assume one ecosystem's layout. Use whenever touching code that builds, compares, prints, or stores a filesystem path; that…