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 y-si-lo-encuentro-quegit 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/y-si-lo-encuentro-que)<a href="https://agentmods.dev/skills/mcasillas17/mexican-mom/y-si-lo-encuentro-que"><img src="https://agentmods.dev/badge/skills/mcasillas17/mexican-mom/y-si-lo-encuentro-que/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/y-si-lo-encuentro-que"><img src="https://agentmods.dev/badge/skills/mcasillas17/mexican-mom/y-si-lo-encuentro-que.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.00059 | $0.00695 |
| Opus 5 | $0.00030 | $0.00347 |
| Sonnet 5 | $0.00012 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
y-si-lo-encuentro-que 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
¿Y si voy y lo encuentro, qué te hago?
You do not get to say "not found" yet.
Rule
Absence is a finding, and it requires evidence exactly like presence does. You may not report that something does not exist until you have searched every way it could plausibly be named or stored, and your report must name the searches you ran.
Procedure
Find the row matching what you are looking for. Run all of its searches before concluding anything.
| Looking for | Run all of |
|---|---|
| File or path | Glob the exact name; glob a distinctive fragment; list the directory it would obviously live in |
| Symbol, function, class | Grep the exact identifier; grep a distinctive substring (catches prefixes, renames, casing); read the file it would obviously live in |
| Config key or env var | Grep the key repo-wide; check the stack's known config locations; check example and template files (.env.example, *.sample, defaults) |
| Route or endpoint | Grep the path string; grep the handler name; read the router or registration file |
| Dependency | Read the manifest (package.json, pyproject.toml, Cargo.toml, go.mod); grep the import name; check the lockfile |
Then answer the two questions that catch most false negatives:
- Could it be named something else? Abbreviated, pluralized, prefixed, hyphenated instead of underscored, or in another language.
- Am I looking in the right tree? Right branch, right worktree, right package in a monorepo — and not excluding a vendored or ignored directory out of habit.
Evidence
Report the searches themselves, not the fact that you searched:
Searched for
getUserPrefs: grep for the identifier (0 hits), grep forUserPref(0 hits), readsrc/user/(12 files, none matching). It is not in this repository.
"I looked and couldn't find it" is not evidence. It is the thing this skill exists to stop.
Boundary
- Claims about external libraries, APIs, or platform behavior —
cadena-de-whatsapp. - Claims that your own work succeeded —
a-ver-ensename. - This skill governs one sentence only: "it isn't there."
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 · 65 lines · 59 tokens per session scan A 5fbf61a829a4
y-si-lo-encuentro-que is a skill published in the GitHub repository mcasillas17/mexican-mom (2 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 695 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
shipkit-feedback-bug
Process user feedback into investigated bug specs with root cause analysis. Triggers: 'triage feedback', 'process bug reports', 'user testing feedback'.
shipkit-codebase-audit
Audit a codebase for dead code, orphaned modules, unused dependencies, and unwired seams. Quick tier runs knip-class checks ephemerally (no repo mutation); deep and exhaustive tiers add intent↔code reconciliation. Portable to any repo, including ones with no tooling installed.
investigate
Deep investigation of bugs, performance issues, or unexpected behavior. TRIGGER THIS SKILL when users report bugs, errors, performance regressions, unexpected behavior, or ask to investigate, debug, diagnose, or find the root cause of any issue — whether they say "why is this broken", "investigate this bug", "find the…
debug
Debug and fix failing tests or errors.
dead-code
Identify unused code (functions, imports, exports, variables, types, classes) and propose cleanup. Use this skill when the user says "find dead code", "unused code", "clean up unused", "code hygiene", "find unused imports", "what can I delete", or any variation of wanting to identify and remove code that is no longer…
question
Answer a question about how things are right now — this codebase, its history, its behavior, a library, an error. Investigates and answers with evidence. Changes nothing, ever.