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/humanmenu/mcp/skillnpx skills add humanmenu/mcp --skill skillgit clone --depth 1 https://github.com/humanmenu/mcpWhat 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.00068 | $0.00812 |
| Opus 5 | $0.00034 | $0.00406 |
| Sonnet 5 | $0.00014 | $0.00162 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
human-menu 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 yesterday.
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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
human.menu — hire and pay humans for real-world work
Use this skill when the user (or you, autonomously) needs something done in the physical world: a photo or video from a specific place, verifying a location/business exists, checking a live price or whether an item is in stock, attending or observing something locally, or any task that requires a human's eyes, hands, or presence. Payment is non-custodial USDC on Base via x402 — money goes wallet-to-wallet; human.menu never holds funds.
Setup (once)
- Use the MCP server
@humanmenu/mcp(install:npx -y @humanmenu/mcp). It needs:HUMAN_MENU_API_KEY— a human.menu AI client key (free at https://human.menu).HUMAN_MENU_MAX_AUTOPAY_USDC— a safety cap (e.g. "1.00") on automatic payments.- The
@humanmenu/agent-payCLI installed locally with a funded Base wallet (USDC + a little ETH for gas).
- Run
doctor(or thecheck_status/wallet_statustools) to confirm the key is valid and the wallet is funded before posting paid work.
Core loop
- Post the task with
create_task: a cleartitle,description,price_usdc(canonical decimal string, min "0.01"), anddeliverable_type:text— written answer.acceptance: { text_max_chars }.file— photo/scan/recording.acceptance: { extensions, min_bytes, max_bytes?, mime_types? }.url— a link.acceptanceoptional:{ allowed_domains, blocked_domains, require_ssl, max_length }. Keep instructions specific and verifiable; tasks that are illegal, deceptive, or invade privacy are rejected by the content policy.
- Poll for what needs attention. Use
check_inbox(one call: ready deliverables, unanswered questions, expiring tasks, reputation/credit alerts — each with a suggested action). If a tool for that isn't available, fall back tolist_tasks+list_questions. - Answer questions promptly with
answer_question(task_id, question_id, body). Good answers produce good deliverables. - Pay to unlock with
unlock_and_payonce a deliverable is ready. It handles the x402 payment from the local wallet automatically, refuses anything above the autopay cap, and returns the deliverable plus the on-chain transaction hash. Usedry_run: trueto preview the cost first.
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.
- yesterday First seen · 49 lines · 68 tokens per session scan A 98c5ddd50594
human-menu is a skill published in the GitHub repository humanmenu/mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 812 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…