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 mcasillas17/mexican-mom --skill frijoles-en-el-tuppergit clone --depth 1 https://github.com/mcasillas17/mexican-momWrote 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/mcasillas17/mexican-mom/frijoles-en-el-tupper)<a href="https://agentmods.dev/skills/mcasillas17/mexican-mom/frijoles-en-el-tupper"><img src="https://agentmods.dev/badge/skills/mcasillas17/mexican-mom/frijoles-en-el-tupper/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/mcasillas17/mexican-mom/frijoles-en-el-tupper"><img src="https://agentmods.dev/badge/skills/mcasillas17/mexican-mom/frijoles-en-el-tupper.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.00065 | $0.01180 |
| Opus 5 | $0.00032 | $0.00590 |
| Sonnet 5 | $0.00013 | $0.00236 |
| Haiku 4.5 | $0.00006 | $0.00118 |
Grade A, and why
frijoles-en-el-tupper 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 12d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dice helado, pero son frijoles
The next person will believe the label.
Rule
A name is a promise about its contents. Every identifier, field, file, key, and comment must let a reader predict what is inside without opening it. When the label and the contents disagree, one of them changes — you do not get to keep both and rely on the reader knowing better.
Procedure
- List the labels in play. Every name introduced, renamed, or touched in this change: functions, parameters, variables, types, struct fields, files, schema columns, API fields, config keys — plus every comment or docstring attached to code you edited. This is a bounded list from the diff, not a tour of the repository.
- Write what each name predicts, before reading the body. One sentence: what it returns, what it changes, what unit it is in, what it holds.
- Read the actual contents — the body, the value, the file — and compare against your sentence.
- Check each name against the known lies. These are the ones that survive review because everyone in the codebase has already adapted to them.
| The label | What is actually inside | The fix |
|---|---|---|
get*, is*, find*, format*, parse* |
It also writes, sends, caches, mutates an argument, or throws where a miss is normal | Rename to the verb that dominates (fetchAndCacheUser), or move the effect out of the function |
| A comment or docstring | Behavior the code stopped having; a parameter that no longer exists; a warning about a bug that was fixed | Rewrite it from the current code, or delete it — a stale comment outranks the code in the reader's head |
| A type | string that is really a fixed set; T | null that is never null; any, object, or dict standing in for a shape the code already assumes |
Narrow it to the enum, union, or declared shape the code relies on |
| A config key or numeric constant | A unit or scale the name does not state — timeout: 30, size: 5, delay: 0.5 |
Put the unit in the name (timeoutMs, maxSizeMb) or in the type |
| A boolean | false means something ambiguous — disableCache, notReady, skipValidation, noRetry |
Name the positive state (cacheEnabled, ready) so both values read in one direction |
| A file or module | A subset of what it now holds, or the one thing it was originally extracted for | Rename the file, or move the strangers out of it |
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.
- 12d ago First seen · 85 lines · 65 tokens per session scan A e001d8e62d1b
frijoles-en-el-tupper is a skill published in the GitHub repository mcasillas17/mexican-mom (2 stars, last pushed 29d ago), licensed MIT. It adds 65 tokens to every session and 1,180 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
implement
Implement a ticket or feature with proportional planning, test first behavior changes, independent review when available, and verification through the real affected surface.
claude-friends
Ask AIs from other families to review something before you commit to it. User-triggered, never automatic. Fires when the user signals uncertainty or asks for another perspective: 'ask a friend', 'second opinion', 'sanity check', 'cross-check', 'am I missing something', 'stress-test this', 'critique this', 'devil's…
lint-drupal-module
Lint review completo de un módulo Drupal 11 combinando 4 fuentes en paralelo — PHPStan level 5 + phpstan-drupal, PHPCS Drupal/DrupalPractice, agente drupal-qa (estándares) y agente drupal-security (OWASP). Dos modos — completo (todo el módulo) y diff (solo archivos cambiados vs develop). Genera informe markdown…
codex-diff-develop
Revisa el diff de la rama actual frente a develop en proyectos Drupal 11 siguiendo la metodología Codex (lógica de negocio, edge cases de hooks/queries, seguridad, performance, completitud). Genera un informe .md en la carpeta del IDE detectado (.antigravity/, .cursor/, .vscode/ o docs/) con hallazgos por severidad y…
codex-pr-review
Revisa pull requests en proyectos Drupal 11 (u otro) siguiendo la metodología Codex (lógica de negocio, edge cases de hooks/queries, seguridad, performance, completitud). Genera un informe .md en la carpeta del IDE detectado (.antigravity/, .cursor/, .vscode/ o docs/) con hallazgos por severidad y soluciones…
shipkit-review-shipping
Review changes across 12 quality dimensions and report findings. Use after a chunk of work or before commit.