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 megamen32/LastHumanCommit --skill real-use-testinggit clone --depth 1 https://github.com/megamen32/LastHumanCommitWrote 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/megamen32/lasthumancommit/real-use-testing)<a href="https://agentmods.dev/skills/megamen32/lasthumancommit/real-use-testing"><img src="https://agentmods.dev/badge/skills/megamen32/lasthumancommit/real-use-testing/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/megamen32/lasthumancommit/real-use-testing"><img src="https://agentmods.dev/badge/skills/megamen32/lasthumancommit/real-use-testing.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.00048 | $0.00723 |
| Opus 5.5 | $0.00019 | $0.00289 |
| Sonnet 5.5 | $0.00010 | $0.00145 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
real-use-testing 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Real Use Testing
Use when a user-facing claim needs real-surface proof. This is the final gate before "done"; test files never substitute for it. The journey executed is the minimal path's shortest real canary, not an invented broader tour.
Full requires a fresh independent Tester after coherent technical review.
Lead's own canary cannot replace that gate. Use $user-testing for standalone
goal-driven attempts and $focus-groups when varied goals add value. Repair
observed in-scope failures and repeat the affected real journey until accepted.
Interaction tool ladder
Climb from the best available rung. Never claim an action is impossible before trying the last one.
- Accessibility tree first, as far as possible. Take an a11y snapshot
(
take_snapshot, accessibility tree, screen-reader structure). Target elements by role + accessible name + stable ref. This is the cheapest and most reliable targeting and usually suffices for the whole journey. - Improved agent/browser MCPs when available and suitable:
browserclaw— a11y snapshot + numbered ref targeting, agent-first;touchpoint— accessibility tree across desktop apps, not just browsers;agent-browser— high-level agent browser automation;playwright-mcp/chrome-devtools-mcp— pages, network, console, screenshots, performance.
- CDP / Playwright scripting when no MCP fits the surface or precise network/console evidence is required.
- Raw XY coordinate clicks + keyboard as the last resort. Some surfaces respond only to real coordinates. ALWAYS try this rung before reporting a UI action as impossible, and verify every coordinate hit with a fresh snapshot or screenshot.
Ladder discipline: after any navigation or state change, re-snapshot before the next action; a stale ref means re-snapshot, never guess; confirm each decisive action by observed state, not by command success. On a browser error, timeout or ambiguous UI state, capture and inspect a secret-safe screenshot in the owning session before retry, navigation or cleanup. If capture is unavailable, record the missing evidence and capability limit.
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 Changed · +9 lines a02a0807bf05
- 1mo ago First seen · 58 lines · 48 tokens per session scan A 8f6e305e396f
real-use-testing is a skill published in the GitHub repository megamen32/LastHumanCommit (2 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 723 once invoked, about $0.0002 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 skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…