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 agentmods add skills/ariaxhan/kernel-claude/human-passnpx skills add ariaxhan/kernel-claude --skill human-passgit clone --depth 1 https://github.com/ariaxhan/kernel-claudeWrote 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/ariaxhan/kernel-claude/human-pass)<a href="https://agentmods.dev/skills/ariaxhan/kernel-claude/human-pass"><img src="https://agentmods.dev/badge/skills/ariaxhan/kernel-claude/human-pass.svg" alt="Measured on agentmods" 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 | $0.00057 | $0.00986 |
| Opus 5 | $0.00028 | $0.00493 |
| Sonnet 5 | $0.00011 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
human-pass 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 4d 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
Each step gives:
- The exact control, named as it appears on screen. Mine the real labels from the UI source; never invent or paraphrase them.
- The exact input, paste-ready. Real URLs, real ids, real values, one per line.
- What should happen, in one sentence.
- What counts as a bug, when that is not obvious. Known rough edges get named so the human does not go hunting for something already on the board.
The tension is real and worth naming when it bites: more coverage per pass, or more passes. Prefer one thorough pass over three thin ones. When a finding will obviously force a rebuild, say so in the same breath, so the next pass is expected rather than a surprise.
Until that verdict exists, the release is not done, whatever CI says.
<on_complete> Report where the guide is, the time it should cost, the single worst-case check it opens with, and what the verdict unlocks. </on_complete>
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.
- 4d ago First seen · 100 lines · 57 tokens per session scan A 5fb4ebe6546b
human-pass is a skill published in the GitHub repository ariaxhan/kernel-claude (12 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 986 once invoked, about $0.0003 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-30.
Other skills, from other repositories
prolong
Recover and use durable coding-session history from PRO-LONG's local append-only log. Use on long-running coding tasks, after context compaction or session resume, when reconstructing prior decisions or tool results, or before repeating work that may already have been attempted.
lemmalog
Externalize working memory and logical state into the lemmalog Datalog engine (MCP). Use for ANY multi-step task where state should outlive one context window or span agents: long investigations, debugging sessions, audits, multi-agent searches, systematic explorations, planning with many interdependent constraints…
causal-memory
Causal memory for agents — install/setup the causal-memory MCP server, then record decisions/outcomes and recall them before acting. Trigger when the user asks to install or set up causal-memory/agent memory, when causal-memory MCP tools are available and the agent faces a non-trivial decision (architecture, debugging…
add-integration-test
Use when adding an end-to-end test scenario to remindb — symptoms include "test the full pipeline", "simulate an agent session", "verify compile→search→fetch flow", "test MCP tools end-to-end", or any task that creates a new Test in integrationtest.go / mcpintegrationtest.go at the repo root. Distinct from per-package…
Browser Smoke Testing
Open a local web target and verify that the main page renders and core controls respond.
Visual Regression Review
Compare browser-rendered UI state against expected layout, content, and responsive behavior.