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-consistency-checkgit 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-consistency-check)<a href="https://agentmods.dev/skills/human-avatar/skills-for-humanity/s4h-logic-consistency-check"><img src="https://agentmods.dev/badge/skills/human-avatar/skills-for-humanity/s4h-logic-consistency-check/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-consistency-check"><img src="https://agentmods.dev/badge/skills/human-avatar/skills-for-humanity/s4h-logic-consistency-check.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.00124 | $0.01220 |
| Opus 5 | $0.00062 | $0.00610 |
| Sonnet 5 | $0.00025 | $0.00244 |
| Haiku 4.5 | $0.00012 | $0.00122 |
Grade A, and why
s4h-logic-consistency-check 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logic Consistency Check
Requirements drift. Specs accumulate. A document written over weeks by multiple people — or a set of decisions made incrementally — can contain contradictions that nobody noticed because each piece was reviewed in isolation.
This skill reads the whole and finds where the parts disagree.
Your Process
Step 1: Map the claims Before checking for consistency, inventory what the document asserts:
- Goals and objectives stated
- Constraints and non-negotiables stated
- Assumptions stated or implied
- Decisions and their stated rationale
- Any numbered requirements or acceptance criteria
This map is what gets checked for internal coherence — not whether any claim is true, but whether the claims are consistent with each other.
Framing check: Confirm the specific document or set of claims before continuing. State what you've identified — the actual object being analyzed and its key parameters (document type, scope, primary claims in tension) — in one sentence, then use AskUserQuestion:
- Question: "I'm reading this as: [your one-sentence framing of the specific document or claim set being checked]. 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: Check goal-constraint conflicts Do the stated goals require violating stated constraints? Common patterns:
- A performance goal that requires more resources than the budget allows
- A simplicity goal combined with a feature list that requires complexity
- A timeline that requires skipping steps the quality requirements depend on
Step 3: Check requirement-requirement conflicts Do individual requirements contradict each other?
- Two requirements that can't both be satisfied simultaneously
- A requirement that is a special case of another requirement but handled differently
- Requirements that use the same term with different implicit meanings (equivocation across requirements)
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 · 120 lines · 124 tokens per session scan A ec53886fa834
s4h-logic-consistency-check is a skill published in the GitHub repository human-avatar/skills-for-humanity (223 stars, last pushed 1mo ago), licensed MIT. It adds 124 tokens to every session and 1,220 once invoked, about $0.0006 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…