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 saadshahd/moo.md --skill humgit clone --depth 1 https://github.com/saadshahd/moo.mdWrote 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/saadshahd/moo.md/hum)<a href="https://agentmods.dev/skills/saadshahd/moo.md/hum"><img src="https://agentmods.dev/badge/skills/saadshahd/moo.md/hum/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/saadshahd/moo.md/hum"><img src="https://agentmods.dev/badge/skills/saadshahd/moo.md/hum.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.00046 | $0.01093 |
| Opus 5.5 | $0.00018 | $0.00437 |
| Sonnet 5.5 | $0.00009 | $0.00219 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
hum 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read first, then ask. Every question leads with what the repo showed and a proposal to accept or change.
Read
Run bunx hum setup scan (the pinned engine: bun add --exact @moo.md/hum@<version> first if package.json has none). It prints the scan, a proposal for each setting, the waiting states, how many open issues the label map covers, and gitIdentity: the name and email hum will commit as, read from your git config. If gitIdentity.found is false, stop: tell the owner to set the missing keys with git config --global <key> "<value>" and ask nothing more. Answer nothing from the scan that the repo already says.
Ask
Ask in this order. One question per turn, each with its proposal. Where a question is open-ended, call hope:elicit; where the answer is a rule others must apply the same way, call hope:anchor; where a setting steers unattended work, call hope:target.
| Ask | Proposal comes from | The answer sets |
|---|---|---|
| Where runs happen: your Mac, CI, or both | the scan: CI workflows, a service unit | runPlaces |
| Which commands a change must pass | CI jobs on pull requests, else package scripts, after the lockfile install a fresh clone needs | checks |
| For CI runs: the repo's setting "Allow GitHub Actions to create and approve pull requests" | workflowsMayOpenPullRequests in the scan; if off, ask the owner to turn it on and never change it yourself |
nothing written |
| For CI runs: the runner, job container and env the wake job runs with | wakeJob in the proposal: the job that runs Claude Code, else the pull request job; drop env only that job uses. The image needs git, node and npm; one that runs as root needs IS_SANDBOX set to 1 in ciEnv. An env value that reads a secret reaches only the step that runs hum |
ciRunner, ciContainer, ciEnv |
For CI runs, when the owner names a runner GitHub does not host and isPublicRepo in the scan is not false: whether wakes may run there |
the proposal never names one; such a machine keeps what a wake leaves, and a wake holds the owner's secrets | "ownRunnerOnPublicRepo": true beside hum in the answers, only on the owner's yes |
| For CI runs: how Claude Code signs in | wakeJob.ciClaudeAuth: the CLAUDE_CODE_OAUTH_TOKEN secret, or env where ciEnv carries the credentials, such as a gateway's settings |
ciClaudeAuth |
| For CI runs: how a pull request's required checks start | a pull request opened with the workflow token starts no workflows, and dispatching the check workflow does not satisfy the required check; ask for a GitHub App with contents, issues and pull requests write, whose two secrets wakeJob.pullRequestToken names where a workflow already mints a token, or a fine-grained token's secret |
pullRequestToken |
| One question per waiting state: after how many hours it ends stuck | waits in the scan |
waitHours |
| What each folder's risk is | folder history and names | paths, strictPaths |
| Which paths hold data or secrets | the scan's matches | strictPaths |
| How many merged changes judge a fix or a measure | the shipped windows | changeLabels.fixWindow, measureWindow |
| Which label means which kind | issue-template labels and repo labels | kindLabels |
| Services and setup each run slot needs | compose file, env script, install command | runSlots |
When ciClaudeAuth is oauth-token: the date the CI token expires, after claude setup-token |
only the owner holds it | a reminder the owner keeps |
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 Changed · +3 lines 29117f046b3b
- 2d ago First seen · 41 lines · 46 tokens per session scan A 551c78c4f5d2
hum is a skill published in the GitHub repository saadshahd/moo.md (38 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,093 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-11-12.
hum compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| humsaadshahd/moo.md | Skill | 38 | yesterday | MIT | A | 46 | Claude Code |
| session-recapsxhmilyoyo/sundayhao-plugins | Skill | 8 | 2d ago | Apache-2.0 | A | 39 | Claude Code |
| knowledge-bank-lookupsxhmilyoyo/sundayhao-plugins | Skill | 8 | 2d ago | Apache-2.0 | A | 94 | Claude Code |
| kb-ingestsxhmilyoyo/sundayhao-plugins | Skill | 8 | 2d ago | Apache-2.0 | A | 152 | Claude Code |
| kb-lintsxhmilyoyo/sundayhao-plugins | Skill | 8 | 2d ago | Apache-2.0 | A | 103 | Claude Code |
| session-managersxhmilyoyo/sundayhao-plugins | Skill | 8 | 2d ago | Apache-2.0 | A | 49 | Claude Code |
| lark-openapi-explorerDropFan/claude-code-plugins | Skill | 8 | 25d ago | MIT | A | 76 | Claude Code |