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/bailutingyu/openbyline/source-verificationnpx skills add bailutingyu/OpenByline --skill source-verificationgit clone --depth 1 https://github.com/bailutingyu/OpenBylineWhat 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.00043 | $0.00611 |
| Opus 5 | $0.00022 | $0.00305 |
| Sonnet 5 | $0.00009 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
source-verification 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.
What it actually says
来源核验与反幻觉
标注格式（[来源]/[待核]/[未证实]）、"宁标不编"与定稿交付闸门见 skill: handoff-protocol §四；本 skill 专讲来源层级、思维链自查、成稿来源呈现规范（核查层 vs 呈现层分离）。
交叉核对
关键数字至少 2 个独立来源；核验来源是否真实存在（防虚构链接/案例/判决）；标注信息时效。
思维链自我核查（逐条套用）
"支持该主张的证据有哪些？可能的反驳或例外是什么？置信度 1-10 打几分？" 置信度低或找不到证据 → 降级为 [待核] 或删除。
优先来源层级
官方/一手 > 权威媒体/学术 > 行业报告 > 二手转述 > 自媒体。
成稿来源呈现规范（正文不露二手出处——核查层与呈现层分离）
- 核查层（research-dossier / draft 的 [来源] 标注）：照常标全，供 fact-checker 核查；来源尽量追到一手（官方公告/当事人原话/原始报道如 Axios、路透、官方发布会），把公众号/自媒体只当"发现线索"，不当最终引用源。
- 呈现层（final 正文）：
- 正文绝不出现"据 XX 公众号 / XX 那篇文章 / 某号写道 / 据某媒体"这类二手转述措辞。事实直接陈述成"谁做了什么、谁说了什么"（一手口径），让文章读起来是作者从一手信息里提炼的观点，而不是把别人公众号二次加工成三手四手——那样一看就是搬运，读者不想看。
- 行内 [来源] 标注一律清除（定稿不留）。
- 确需注明出处，统一放文末"信息来源"小块，且只列一手信源（发布会/官方/当事人/原始报道），不列二手公众号名。
一句话：来源在核查层追到一手、标到牙齿；在成稿层干净到看不见，最多文末一行。
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 · 22 lines · 43 tokens per session scan A c85efeb29bdb
source-verification is a skill published in the GitHub repository bailutingyu/OpenByline (2 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 611 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…