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 tranfu-labs/tranfu-skills --skill solution-sourcinggit clone --depth 1 https://github.com/tranfu-labs/tranfu-skillsWrote 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/tranfu-labs/tranfu-skills/solution-sourcing)<a href="https://agentmods.dev/skills/tranfu-labs/tranfu-skills/solution-sourcing"><img src="https://agentmods.dev/badge/skills/tranfu-labs/tranfu-skills/solution-sourcing/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/tranfu-labs/tranfu-skills/solution-sourcing"><img src="https://agentmods.dev/badge/skills/tranfu-labs/tranfu-skills/solution-sourcing.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.00145 | $0.01463 |
| Opus 5 | $0.00072 | $0.00732 |
| Sonnet 5 | $0.00029 | $0.00293 |
| Haiku 4.5 | $0.00015 | $0.00146 |
Grade A, and why
solution-sourcing 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 9d 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
方案来源方法论（Solution Sourcing）
本 Skill 回答一个问题：方案从哪里来。默认坏习惯是"接到问题就自己想"——正确姿势是先判定问题的类型，类型决定去哪里找方案、怎么验证。
主干五步（所有类型共用）
- 定义问题与成功判据：先写下"什么算解决/什么算成功"，再去找方案。判据先于方案存在，防止拿着锤子找钉子。
- 来源扫描：方向由类型决定（见判型表）——向外搜、向内采证、或做 spike。
- 候选 ≥2 与取舍：至少两个可行候选，且把"什么都不做/维持现状"列为基线候选之一。逐候选写代价，不假装没有代价。
- 最小验证：用最小成本证实或证伪关键假设——spike、原型、基线测试。影响面越大、可逆性越差，越必须先验证再拍板。
- 决策落盘：项目用 openspec 就写进当前 change 的 design.md；否则遵循项目自己的决策记录惯例。落盘必须含「现有方案调研」小节（见下）。
判型表
| 型 | 触发场景 | 来源扫描方向 | 最小验证形态 |
|---|---|---|---|
| A 引入型 | 要做新模块 / 新能力（状态管理、富文本、鉴权……） | 先搜市面成熟方案：英文网络最佳实践、活跃开源项目、同类产品做法 | spike 或最小集成验证 |
| B 障碍型 | 实现途中撞上具体技术问题（怪 bug、性能墙、平台限制） | 先假设"别人一定遇到过"：搜已知解法、官方 issue、社区讨论 | 本地复现 + 验证解法 |
| C 退化型 | 代码异味、维护性下降、bug 向同一结构聚集 | 内部证据为主：软信号采集 + 归因；外部只查"业界对这类结构的惯例" | 护栏先行——先补行为基线测试再动刀 |
| D 探索型 | 新领域，市面没有成熟方案 | 时间盒 spike，两个方案对比胜于一个方案迭代 | 判据先行的对比实验，产物进原型区不进主干 |
各型最小动作清单
A 引入型
- 搜索关键词至少覆盖：问题域英文名 + "best practices"、候选库名 + "comparison / alternatives"。
- 候选评估维度：维护活跃度、与现有技术栈契合度、迁移成本、锁定风险。
- 纪律：buy-before-build——自建必须写明"为什么每个现成候选都不适用"，写不出来就用现成的。
- 反向纪律：不追潮流——"更新/更火"不构成理由，收益必须落在本项目的具体判据上。
B 障碍型
- 时间盒更短：先花 10–20 分钟搜已知解法，再决定是否自己深挖。
- 找到解法后必须本地复现问题 + 验证解法，不直接照抄粘贴。
- 解法影响公共结构（依赖版本、构建配置）时升级为 A 型走完整评估。
C 退化型
- 判据是变化理由的条数，不是行数。软信号（超长函数、超多公开方法、状态字段堆积、同文件反复探针阅读）只触发复核，不直接触发重构。
- 归因先于动刀：回答"这个结构有几条会独立变化的理由"，按用例纵切，不按技术层横切。
- 硬约束：行为不变是第一属性；护栏先行，覆盖不足的分支先补行为基线测试（用 commit 顺序证明）；发现真 bug 只登记不顺手修。
- 收益必须诚实归因，净收益为零就写零。
D 探索型
- 先写成功判据和时间盒，到点强制收敛，防止无限探索。
- 至少两个正交方向的尝试对比，胜者进入 A/B 型流程正式化。
- 产物落在项目的原型区（如
prototypes/），不直接进主干。
「现有方案调研」小节格式
A / B 型方案文档必须包含此小节，作为放行前置：
## 现有方案调研
- 候选1：<名称>（<出处链接/来源>）——<不采用理由 / 采用理由>
- 候选2：……
- 基线候选（什么都不做）：<维持现状的代价>
- 结论：<采用谁，或为什么自建>
缺此小节的 A/B 型方案，评审方应打回，不进入实现。
与项目契约的关系
本 Skill 只定义跨项目稳定的方法论。项目和团队契约（AGENTS.md、角色文件、openspec 约定）定义谁判型、谁调研、谁打回；两者冲突时，当前生效的项目契约优先。
What ships with it
5 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.
- 9d ago First seen · 75 lines · 145 tokens per session scan A 1ba1400693e1
solution-sourcing is a skill published in the GitHub repository tranfu-labs/tranfu-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 145 tokens to every session and 1,463 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…