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 beginnersinai/the-44-percent-rule --skill map-commandgit clone --depth 1 https://github.com/beginnersinai/the-44-percent-ruleWrote 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/beginnersinai/the-44-percent-rule/map-command)<a href="https://agentmods.dev/skills/beginnersinai/the-44-percent-rule/map-command"><img src="https://agentmods.dev/badge/skills/beginnersinai/the-44-percent-rule/map-command/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/beginnersinai/the-44-percent-rule/map-command"><img src="https://agentmods.dev/badge/skills/beginnersinai/the-44-percent-rule/map-command.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.00069 | $0.04786 |
| Opus 5 | $0.00034 | $0.02393 |
| Sonnet 5 | $0.00014 | $0.00957 |
| Haiku 4.5 | $0.00007 | $0.00479 |
Grade A, and why
map 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 9d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 9d ago First seen · 376 lines · 69 tokens per session scan A fddb9faeb00e
map is a skill published in the GitHub repository beginnersinai/the-44-percent-rule (2 stars, last pushed 4mo ago), with no licence file. It adds 69 tokens to every session and 4,786 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
la-chancla
Use only when the user explicitly requests a strict review of one named task, change, plan, release, or invariant. Never self-selected, never auto-loaded, never invoked by another skill or by the mexican-mom router. NOT a session-wide mode and NOT a warning counter.
mexican-mom
Use only when the user explicitly asks for mexican-mom, mom, or la jefa — routes to the right discipline skill or shows the index.
a-ver-ensename
Use before claiming your own work is fixed, passing, complete, compatible, secure, built, or deployed — the claim requires artifact output produced since the latest change. NOT for unverified external library or API facts; use cadena-de-whatsapp. NOT for claiming a repo artifact is absent; use y-si-lo-encuentro-que.
ahorita-es-ahorita
Use when one task must preempt all other work — the user explicitly says stop, a production outage, a leaked or committed secret, an active security incident, a red build blocking the team, a broken critical path. NOT for time estimates, TODOs, or deferrals; use ahorita.
frijoles-en-el-tupper
Use when writing or reviewing names — functions, variables, types, files, schemas, API fields, config keys — and the comments attached to them, to check that each label predicts what is actually inside. NOT for whether failure paths are handled; use pero-ponte-sueter.
me-estas-avisando-o-pidiendo-permiso
Use before an action needing the user's explicit consent: force-push, history rewrite, dropping a table, deleting a directory, publishing or releasing, sending real email, spending money, or anything touching production or a shared environment. NOT for creating the rollback path; use por-si-se-ocupa.