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/ryosukesama/github-ai/research-with-sourcesnpx skills add RyosukeSAMA/github-ai --skill research-with-sourcesgit clone --depth 1 https://github.com/RyosukeSAMA/github-aiWrote 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/ryosukesama/github-ai/research-with-sources)<a href="https://agentmods.dev/skills/ryosukesama/github-ai/research-with-sources"><img src="https://agentmods.dev/badge/skills/ryosukesama/github-ai/research-with-sources.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.00035 | $0.00199 |
| Opus 5 | $0.00017 | $0.00100 |
| Sonnet 5 | $0.00007 | $0.00040 |
| Haiku 4.5 | $0.00003 | $0.00020 |
Grade A, and why
research-with-sources 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
Research with Sources
Work as Athena. Accuracy and traceability matter more than volume.
Workflow
- Define the exact question, date sensitivity, and decision the answer supports.
- Prefer primary sources such as official documentation, research papers, laws, product pages, and first-party announcements.
- Cross-check important claims when independent authoritative sources exist.
- Record dates because publication date and event date may differ.
- Separate directly supported facts, reasonable inference, and uncertainty.
- Present a concise answer first, then evidence and practical implications.
- Place source links beside the claims they support.
Do not fabricate citations. If browsing or connected research tools are not available, say that live verification was not performed and identify the exact sources that should be checked.
What ships with it
2 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.
- 5d ago First seen · 24 lines · 35 tokens per session scan A 66c464f20384
research-with-sources is a skill published in the GitHub repository RyosukeSAMA/github-ai (5 stars, last pushed 22d ago), licensed MIT. It adds 35 tokens to every session and 199 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
typescript-expert
TypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.
final-release-review
Perform pre-release planning or a final release-candidate review for openai-agents-python by comparing the target with the previous remote tag, determining the minimum compatible release type, auditing regressions and contract changes, reviewing open documentation PR coverage, drafting minor-release Key Changes, and…
release-candidate-prep
Preflight and prepare an OpenAI Agents Python release candidate in a dedicated worktree from exact origin/main, gate readiness before branch creation, freeze the released API contract, create or replace the local release branch with one release commit, enforce final release review as a checker, and produce…
implementation-strategy
Choose compatibility-aware scope for runtime and API changes in openai-agents-python. Use before initial implementation and each review-feedback batch to decide whether to patch, reset the design, preserve compatibility, or reject unsupported cases.
pr-draft-summary
Create the required PR-ready summary block, branch suggestion, title, and draft description for openai-agents-python. Use before the final response whenever the current task changed runtime code, tests, examples, build/test configuration, or docs with behavior impact, regardless of perceived change size and including…
examples-run-analysis
Analyze artifacts from the latest completed manual examples Make run. Read the main log, every relevant per-example log, and example source; validate every exit-0 example and classify failures, skips, and environment restrictions. Never execute or control examples.