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 keshrath/agent-discover --skill findgit clone --depth 1 https://github.com/keshrath/agent-discoverWrote 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/keshrath/agent-discover/find)<a href="https://agentmods.dev/skills/keshrath/agent-discover/find"><img src="https://agentmods.dev/badge/skills/keshrath/agent-discover/find/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/keshrath/agent-discover/find"><img src="https://agentmods.dev/badge/skills/keshrath/agent-discover/find.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.00050 | $0.00362 |
| Opus 5.5 | $0.00020 | $0.00145 |
| Sonnet 5.5 | $0.00010 | $0.00072 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
find 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 10d 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.
What it actually says
Goal: get a working tool for this need with the fewest calls: $ARGUMENTS
search_toolswith 2-4 short phrasings of the need in one call (queries: [...]). It searches every installed server's indexed tools, enabled or not.- Good hit on an enabled server: call that tool directly (native name
<server>__<tool>), or viacall_toolif it is not in your tool list. - Good hit on an installed but not enabled server:
enable_server, then use the tool. Mention missing secrets from the result instead of calling a tool that will fail. - No good hit:
search_servers(searches local + MCP Registry/npm/PyPI). Pick the best match and callinstall_server. The user is asked for consent with the exact command, env keys and provenance; never install without that approval and never retry a denied install. - Use
get_toolwhen you need the full input schema before calling.
Report in one or two lines what you enabled or installed. Do not paste the result tables back; the user already sees them.
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.
- 10d ago First seen · 16 lines · 50 tokens per session scan A b3e886b87861
find is a skill published in the GitHub repository keshrath/agent-discover (7 stars, last pushed 7d ago), licensed MIT. It adds 50 tokens to every session and 362 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-10-06.
Other skills, from other repositories
gitnexus-cli
Use when the user needs to run GitNexus CLI commands like analyze/index a repo, check status, clean the index, generate a wiki, or list indexed repos. Examples: "Index this repo", "Reanalyze the codebase", "Generate a wiki".
gitnexus-debugging
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug".
gitnexus-refactoring
Use when the user wants to rename, extract, split, move, or restructure code safely. Examples: "Rename this function", "Extract this into a module", "Refactor this class", "Move this to a separate file".
gitnexus-impact-analysis
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?".
gitnexus-exploring
Use when the user asks how code works, wants to understand architecture, trace execution flows, or explore unfamiliar parts of the codebase. Examples: "How does X work?", "What calls this function?", "Show me the auth flow".
gitnexus-guide
Use when the user asks about GitNexus itself — available tools, how to query the knowledge graph, MCP resources, graph schema, or workflow reference. Examples: "What GitNexus tools are available?", "How do I use GitNexus?".