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/kyopark2014/agent-plugins/source-managementnpx skills add kyopark2014/agent-plugins --skill source-managementgit clone --depth 1 https://github.com/kyopark2014/agent-pluginsWhat 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.00035 | $0.01426 |
| Opus 5 | $0.00017 | $0.00713 |
| Sonnet 5 | $0.00007 | $0.00285 |
| Haiku 4.5 | $0.00003 | $0.00143 |
Grade A, and why
source-management 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.
How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Source Management
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.
Knows what sources are available, helps connect new ones, and manages how sources are queried.
Checking Available Sources
Determine which MCP sources are connected by checking your actual tool list. Match tool name patterns to identify connected sources:
| Source | Tool name patterns | Key capabilities |
|---|---|---|
| ~~chat | slack_* (Slack), teams_* (Teams) |
Search messages, read channels and threads |
gmail_*, ms365_* mail tools |
Search messages, read individual emails | |
| ~~cloud storage | google_drive_*, ms365_* file tools |
Search files, fetch document contents |
| ~~project tracker | jira_*, asana_*, linear_* |
Search tasks, typeahead search |
| ~~CRM | salesforce_*, hubspot_* |
Query records (accounts, contacts, opportunities) |
| ~~knowledge base | API-* (Notion), confluence_*, guru_* |
Semantic search, keyword search |
How to detect: Look at your available tools. If you have tools matching a pattern above (e.g., slack_get_channel_history), that source category is connected. Use those tools directly — do not look for ~~ prefixed tools.
Guiding Users to Connect Sources
When a user searches but has few or no sources connected:
You currently have [N] source(s) connected: [list].
To expand your search, you can connect additional sources in your MCP settings:
- ~~chat — messages, threads, channels
- ~~email — emails, conversations, attachments
- ~~cloud storage — docs, sheets, slides
- ~~project tracker — tasks, projects, milestones
- ~~CRM — accounts, contacts, opportunities
- ~~knowledge base — wiki pages, knowledge base articles
The more sources you connect, the more complete your search results.
When a user asks about a specific tool that is not connected:
[Tool name] isn't currently connected. To add it:
1. Open your MCP settings
2. Add the [tool] MCP server configuration
3. Authenticate when prompted
Once connected, it will be automatically included in future searches.
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 · 173 lines · 35 tokens per session scan A cb2a9918f6dd
source-management is a skill published in the GitHub repository kyopark2014/agent-plugins (4 stars, last pushed 25d ago), licensed MIT. It adds 35 tokens to every session and 1,426 once invoked, about $0.0002 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
ask-zilliz
Zilliz Cloud onboarding and usage assistant. Helps users understand Zilliz Cloud, choose the right plan, estimate costs, write code, debug issues, and adopt new features like Functions, Volumes, and Global Clusters. Use this skill whenever the user asks about Zilliz Cloud — including plan selection, pricing, cost…
diagnose
Use when the user reports that a Zilliz Cloud cluster or Milvus collection is unhealthy, slow, stuck, returning errors, hitting quotas, or otherwise misbehaving — or when they ask "what's wrong with...", "why is ... slow", "diagnose ...", "troubleshoot ...".
collection
Use when the user wants to create, list, describe, drop, rename, load, release, or manage collections and collection aliases in Milvus.
cluster
Use when the user wants to create, list, describe, delete, suspend, resume, or modify Zilliz Cloud clusters.
external-collection
Use when the user wants to trigger, describe, or list refresh jobs for an external collection (a collection backed by an external data source such as Vector Lake). Note this is the data-plane refresh workflow, not collection CRUD -- for create/drop/load see the collection skill.
backup
Use when the user wants to create, list, describe, delete, export, or restore backups, or manage backup policies on Zilliz Cloud.