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 hewi333/Mom-n-Pop-Skills --skill agent-cheatsheet-buildergit clone --depth 1 https://github.com/hewi333/Mom-n-Pop-SkillsWrote 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/hewi333/mom-n-pop-skills/agent-cheatsheet-builder)<a href="https://agentmods.dev/skills/hewi333/mom-n-pop-skills/agent-cheatsheet-builder"><img src="https://agentmods.dev/badge/skills/hewi333/mom-n-pop-skills/agent-cheatsheet-builder/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/hewi333/mom-n-pop-skills/agent-cheatsheet-builder"><img src="https://agentmods.dev/badge/skills/hewi333/mom-n-pop-skills/agent-cheatsheet-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 35 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Excessive Agency · line 188 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 200 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00064 | $0.01947 |
| Opus 5.5 | $0.00026 | $0.00779 |
| Sonnet 5.5 | $0.00013 | $0.00389 |
| Haiku 4.5 | $0.00006 | $0.00195 |
Grade A, and why
agent-cheatsheet-builder 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Cheat Sheet Builder
What This Does
Generates a one-page cheat sheet for a non-technical business owner so they know exactly what their Hermes agent can do, how to ask for things, and what the agent will never do without their approval. Designed for owners in their 60s who have never used AI — plain English, large print, no jargon.
When to Use
- Onboarding a non-technical owner to their agent for the first time
- After wiring a new integration (email, payments, CRM, marketing) — regenerate
- Part of a hackathon demo or handoff package
- Any small business using Hermes that needs a "fridge sheet" for the owner
How It Works
Step 1: Scan Installed Skills
ls ~/.hermes/skills/productivity/ ~/.hermes/skills/email/ ~/.hermes/skills/payments/
For each skill, read the SKILL.md frontmatter (name + description) to understand what the agent can actually do. Categorize each as:
- Wired — has env vars set, verified working (check .env + verification checklist)
- Documented — skill exists but not wired (checkmarks in verification section)
- Not applicable — skill installed but not relevant to this business
Step 2: Identify the Owner's Real Flows
Map skills to everyday business scenarios the owner recognizes. Examples:
- "When a new lead comes in" → lead-to-payment + email (himalaya)
- "When you need to send a payment link" → stripe-payments
- "When you want to check your contacts" → crm-lite
- "When you want to send a marketing email" → mailchimp-integration
Step 3: Generate the Cheat Sheet
Use the template below. Fill in the business name, owner names, and real flows from the scan. The sheet should be:
- One page (printable on 8.5x11 or A4)
- Large font (14-16pt minimum, headings 18-20pt)
- Plain English — no technical terms without explaining them
- Action-oriented — "Say this → Agent does this"
- Honest about limits — "Agent CANNOT do X" is as important as what it can do
Step 4: Export
Generate as markdown → convert to PDF using pandoc or print directly. Also
save a plain-text version for Telegram delivery.
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 First seen · 201 lines · 64 tokens per session scan A 72db4ca7da46
agent-cheatsheet-builder is a skill published in the GitHub repository hewi333/Mom-n-Pop-Skills (125 stars, last pushed 1mo ago), licensed MIT. It adds 64 tokens to every session and 1,947 once invoked, about $0.0003 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-30.
Other skills, from other repositories
apify-youtube-transcript-scraper
Get YouTube captions, timestamped quotations, SRT/VTT and translated transcripts for videos, channels and playlists through the harshmaur/youtube-transcript-scraper Apify Actor.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
meta-web-to-pdf-briefing
Render a topic into a distributable PDF briefing in three steps: web search → bullet summary → styled PDF. Trigger when the user asks for a PDF briefing on a single topic.
chat-complex-documents
Chat with and search your complex documents — ask questions, extract tables and fields, and get answers grounded in the source. Connects the hosted Unstructured Transform MCP server to parse, structure, and enrich PDFs, Word/Excel/PowerPoint, images, scanned files, emails, and 60+ other formats into clean, AI-ready…
pkf-writing
Author, update, convert, validate, persist, and render PKF (.pkf) content through message-inline, Library Asset, or Memory Page carriers. Use for structured reports, knowledge pages, delivery cards, or any .pkf body. NOT for recall, memory-graph placement, or curation decisions — those belong to the memory skill.