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 agentmods add skills/eldergenix/proofloop/find-skillsnpx skills add Eldergenix/Proofloop --skill find-skillsgit clone --depth 1 https://github.com/Eldergenix/ProofloopWrote 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/eldergenix/proofloop/find-skills)<a href="https://agentmods.dev/skills/eldergenix/proofloop/find-skills"><img src="https://agentmods.dev/badge/skills/eldergenix/proofloop/find-skills.svg" alt="Measured on agentmods" 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 | $0.00067 | $0.01117 |
| Opus 5 | $0.00034 | $0.00558 |
| Sonnet 5 | $0.00013 | $0.00223 |
| Haiku 4.5 | $0.00007 | $0.00112 |
Grade A, and why
find-skills 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 4d 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.
This is a copy
91% identical to find-skills — 20 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Skills
This skill helps you discover and install skills from the open agent skills ecosystem.
When to Use This Skill
Use this skill when the user:
- Asks "how do I do X" where X might be a common task with an existing skill
- Says "find a skill for X" or "is there a skill for X"
- Asks "can you do X" where X is a specialized capability
- Expresses interest in extending agent capabilities
- Wants to search for tools, templates, or workflows
- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
What is the Skills CLI?
The Skills CLI (npx skills) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.
Key commands:
npx skills find [query]- Search for skills interactively or by keywordnpx skills add <package>- Install a skill from GitHub or other sourcesnpx skills check- Check for skill updatesnpx skills update- Update all installed skills
Browse skills at: https://skills.sh/
How to Help Users Find Skills
Step 1: Understand What They Need
When a user asks for help with something, identify:
- The domain (e.g., React, testing, design, deployment)
- The specific task (e.g., writing tests, creating animations, reviewing PRs)
- Whether this is a common enough task that a skill likely exists
Step 2: Search for Skills
Run the find command with a relevant query:
npx skills find [query]
For example:
- User asks "how do I make my React app faster?" →
npx skills find react performance - User asks "can you help me with PR reviews?" →
npx skills find pr review - User asks "I need to create a changelog" →
npx skills find changelog
The command will return results like:
Install with npx skills add <owner/repo@skill>
vercel-labs/agent-skills@vercel-react-best-practices
└ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
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.
- 4d ago First seen · 133 lines · 67 tokens per session scan A 126569842b4f
find-skills is a skill published in the GitHub repository Eldergenix/Proofloop (41 stars, last pushed 3mo ago), licensed MIT. It adds 67 tokens to every session and 1,117 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to find-skills, differing in 20 lines, and is treated as a copy.
Other skills, from other repositories
schedule
Use when scheduling recurring cron jobs or one-shot background notifications.
get-fable
Route and orchestrate the canonical get-fable coding lifecycle — discover, research, plan, build, verify, review, secure, release, recover — from durable .fable state and incoming intent. Use when starting any substantial engineering task, resuming from a handoff, navigating lifecycle phase transitions, or determining…
memory-types-team-stores
Use when configuring shared team memory stores and knowledge graphs.
memory-types
Use when managing persistent project memory, facts, and developer context.
code-review
Use when reviewing code changes, pull requests, or diffs for bugs, security, and quality.
tend-audit
Verify a feature's checks against real evidence. Owns audit.verdicts, runs smoke.cmd if defined, records drift, and is the only path to status = "verified". Trigger after /tend run completes, after /tend discover for a mature codebase, or anytime an honest read on whether a feature actually works is needed.