Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/evoelsewhere/evofluxnpx agentmods add skills/evoelsewhere/evoflux/find-key-internal-sourcesWrote 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/evoelsewhere/evoflux/find-key-internal-sources)<a href="https://agentmods.dev/skills/evoelsewhere/evoflux/find-key-internal-sources"><img src="https://agentmods.dev/badge/skills/evoelsewhere/evoflux/find-key-internal-sources/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/evoelsewhere/evoflux/find-key-internal-sources"><img src="https://agentmods.dev/badge/skills/evoelsewhere/evoflux/find-key-internal-sources.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.00097 | $0.02240 |
| Opus 5 | $0.00048 | $0.01120 |
| Sonnet 5 | $0.00019 | $0.00448 |
| Haiku 4.5 | $0.00010 | $0.00224 |
Grade A, and why
find-key-internal-sources 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 2d 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
100% identical to find-key-internal-sources — 0 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Key Internal Sources
Find the smallest reliable internal route that helps a seller get an answer or unblock work: the right people, maintained docs, public channels, decision forums, and escalation paths. The default output is a quick, evidence-backed routing map plus a draft-ready first ask. This workflow is read-only and never posts, assigns, or updates systems.
Common Skill Instructions
MANDATORY: If not already in context, read and adhere closely to plugins/sales/skills/index/SKILL.md## Cross-Skill Best Practices.
Key Dependency Categories
Use only the categories needed for the selected route; do not fan out across every source by default.
- ~~Knowledge & Files for maintained source-of-truth pages, owner metadata, wikis, field guides, playbooks, FAQs, runbooks, launch docs, and decision records
- ~~Internal Messaging for public channels, channel topics, threads, active contributors, escalation routes, support channels, and decision forums
- ~~CRM for customer or account identity, ownership, opportunity context, and CRM-visible blockers that clarify an account-specific question
Prefer canonical ownership and source-of-truth material over chat mentions. ~~CRM can resolve account truth, but it does not by itself prove who owns the internal answer.
Reference Loading
SKILL.md owns the normal route selection, bounded search, ranking, and output map. Load references only when their extra detail matters:
- Use references/search-patterns.md when query fan-out, compound facets, source-specific search, or stopping rules need more detail.
- Use references/company-context.md only after the generic pass, when user-provided or connector-visible terminology is likely to change the route.
Terms
- Source-of-truth page: the maintained doc, wiki, tracker, or page that should be treated as the most authoritative answer source.
- DRI: directly responsible individual, the person accountable for a topic, decision, or follow-through.
- SME: subject matter expert, someone with practical depth on the topic even if they are not the accountable owner.
- Decision forum: the recurring meeting, channel, doc, or group where tradeoffs and approvals are handled.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 160 lines · 97 tokens per session scan A b63612463f88
find-key-internal-sources is a skill published in the GitHub repository evoelsewhere/evoflux (7 stars, last pushed today), licensed Apache-2.0. It adds 97 tokens to every session and 2,240 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to find-key-internal-sources, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
heartbeat
Periodic heartbeat check that reads HEARTBEAT.md from the workspace and executes any tasks listed there. Use for autonomous background monitoring, periodic maintenance, and proactive task execution. Triggered by a cron schedule.
yutori-computer-use
Run local Mac desktop tasks with Yutori computer use. Use when the user wants to operate macOS apps, websites in a local browser, or cross-app workflows on the visible desktop, or to drive one app's window in the background while they keep working.
jobs
Create and manage scheduled jobs (cron tasks, reminders, heartbeat checks, polling watchers) that vixd runs automatically. Use when the user asks to schedule, automate, monitor, watch, or be reminded about something.
expertise-exchange
Team expertise billboard via adept exchange: ask teammates for expertise and stack responses. Apply when the user wants a colleague's input, mentions the exchange, or when you start using adept — sample open requests and offer to answer ones the user knows about.
ponytail
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports…
pre-post-hooks
Guide for configuring PreToolUse, PostToolUse, and Stop hooks in Claude Code. Use when the user asks about hooks, wants to run commands before/after tool calls, needs auto-formatting, auto-linting, validation gates, or mentions settings.json hook config.