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/surfmind-space/awesome-surfmind/source-listnpx skills add surfmind-space/awesome-surfmind --skill source-listgit clone --depth 1 https://github.com/surfmind-space/awesome-surfmindWrote 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/surfmind-space/awesome-surfmind/source-list)<a href="https://agentmods.dev/skills/surfmind-space/awesome-surfmind/source-list"><img src="https://agentmods.dev/badge/skills/surfmind-space/awesome-surfmind/source-list.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.00077 | $0.00496 |
| Opus 5 | $0.00039 | $0.00248 |
| Sonnet 5 | $0.00015 | $0.00099 |
| Haiku 4.5 | $0.00008 | $0.00050 |
Grade A, and why
source-list 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 5d 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
Source List
Inventory the citations, links, footnotes, and named sources a page relies on, and explain what each one appears to support, flagging anything missing or weak. Never invent bibliographic details, claim to have opened a source that isn't in context or tool output, or treat a link's mere presence as proof it supports the nearby claim.
- Scan the visible page and selected text for citations, links, footnotes, embedded references, and named sources.
- Group duplicate references, and preserve each source's title, organization, author, date, and URL as far as they're visible.
- Explain what each source appears to support on the page, tying it to the specific claim it sits next to.
- Flag references that are missing, circular, promotional, outdated, or not actually connected to the claim they're attached to.
Report a source inventory, what each source supports, source-quality notes, and any missing or weak citations. Preserve exact names, numbers, links, dates, and currencies, and don't infer a source's content from its title alone.
Example
Source: a news article asserting "studies show the drug is safe," linking only to one manufacturer page.
Source inventory:
- Manufacturer product page (vendor.com), no date shown — the article's only link.
- "Studies show…" — referenced in the text but with no citation or link.
What each supports: The manufacturer page backs the company's own safety messaging; the unlinked "studies" are meant to support the safety claim but point to nothing checkable.
Source-quality notes: The only cited source is promotional and self-interested, not independent or peer-reviewed.
Missing or weak citations: The central "studies show it's safe" claim has no source. An independent trial, regulator filing, or systematic review is needed to support it.
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.
- 5d ago First seen · 35 lines · 77 tokens per session scan A 35a1a0bc6281
source-list is a skill published in the GitHub repository surfmind-space/awesome-surfmind (5 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 496 once invoked, about $0.0004 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
cs-master
Expert computer scientist for algorithms, complexity analysis, and distributed systems.
uiux-master
UI/UX expert for design systems, accessibility, and avoiding generic AI-generated design patterns.
c-master
C programming expert for memory management, systems programming, and performance optimization.
data-science
ML engineering expert for feature engineering, model debugging, and production pipelines.
go-master
Go expert for goroutines, channels, microservices, and concurrent patterns.
network-devops
Network performance expert for latency optimization, packet analysis, and infrastructure tuning.