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/kyopark2014/agent-pluginsnpx agentmods add skills/kyopark2014/agent-plugins/source-managementWrote 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/kyopark2014/agent-plugins/source-management)<a href="https://agentmods.dev/skills/kyopark2014/agent-plugins/source-management"><img src="https://agentmods.dev/badge/skills/kyopark2014/agent-plugins/source-management/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/kyopark2014/agent-plugins/source-management"><img src="https://agentmods.dev/badge/skills/kyopark2014/agent-plugins/source-management.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.00035 | $0.01426 |
| Opus 5.5 | $0.00014 | $0.00570 |
| Sonnet 5.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 1mo 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
84% identical to source-management — 35 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 — 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.
- 1mo 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 10d ago), licensed MIT. It adds 35 tokens to every session and 1,426 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 84% identical to source-management, differing in 35 lines, and is treated as a copy.
Other skills, from other repositories
meeting-note-summarizer
Turn meeting notes or transcripts into factual summaries, decisions, questions, and action items. Use when a user wants a concise recap or needs explicit owners and deadlines extracted without filling in missing details.
daily-standup-journal
Generate concise daily standups, reflection prompts, and weekly retrospectives for individuals or teams. Use for planning a day, surfacing blockers, reviewing user-provided entries, or drafting a check-in without assuming prior history.
happiness-skill
A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.
glyph
Render an answer as ASCII art plus semantic emojis inline with no setup questions: one render per reply, verdict first. Use for any answer with shape: status, inventories, audits, budgets, comparisons, rankings, pipelines, 'what is using X', or any ad-hoc 'show me X visually' ask. Not for definitions, conceptual…
prompt-focus
Shows where your attention went from your own Claude Code and Codex prompts: projects, hours and re-typed asks over 20 weeks, as a local counts-only HTML report. Use when asking where your focus goes.
txt-copy
Copy generated text content to clipboard. Use when user asks to "copy this", "copy to clipboard", "save to clipboard", or after creating emails, messages, letters, or other text content that needs to be shared.