Sponsor Finder Skill (awesome-copilot) for Claude Code: What It Does and How to Install It

Makes your agent list which open source dependencies of a GitHub repository you can sponsor, and where to do it.

Installs: 8.7K; on skills.sh
Stars: 40.7K; on GitHub
Updated: Oct 2026; last repo commit

You type /sponsor with a GitHub owner/repo, such as expressjs/express. The agent follows an eight-step workflow: it reads the repo's manifest, pulls the full dependency tree from the deps.dev API, resolves each dependency to a GitHub repo, adds OSSF Scorecard health data, looks for funding links, verifies every link by fetching it, and then groups the results by funding destination.

The report starts with a numbered "Ways to Give Back" list sorted by how many dependencies each sponsor covers, then a coverage summary. It bundles no scripts. SKILL.md tells the agent to use GitHub MCP tools, web_fetch and web_search, and never to clone or shell out.

Good for

Maintainers who want to give back to the projects they depend on
Open Source Program Offices planning sponsorship
Developers checking how well maintained their dependencies are

Install sponsor-finder

Claude Code

Copy this prompt.

Install the sponsor-finder skill in Claude Code. Run this command:

npx skills add https://github.com/github/awesome-copilot --skill sponsor-finder

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Requires Node.js.

The awesome-copilot README is written for GitHub Copilot and does not name Claude Code, so the Claude Code and Codex routes are the standard skill-folder routes. The ospo-sponsorship plugin lists 1 skill and no agents in its plugin.json. The plugin folder on the main branch holds plugin.json and a README only, so check what the install adds. The skill reads repositories with the GitHub MCP server's get_file_contents tool, so install that server too. There is no Claude app upload route because the skill needs that server.

Built from the package data we hold. Not yet tested by us. Source.

What's in the skill

When it loads

Find which of a GitHub repository's dependencies are sponsorable via GitHub Sponsors. Uses deps.dev API for dependency resolution across npm, PyPI, Cargo, Go, RubyGems, Maven, and NuGet. Checks npm funding metadata, FUNDING.yml files, and web search. Verifies every link. Shows direct and transitive dependencies with OSSF Scorecard health data. Invoke with /sponsor followed by a GitHub owner/repo (e.g. "/sponsor expressjs/express").

Sections in SKILL.md

Your Workflow
Step 1: Detect Ecosystem and Package
Step 2: Get Full Dependency Tree (deps.dev)
URL encoding
For repos without a single root package
Step 3: Resolve Each Dependency to a GitHub Repo (deps.dev)
Efficiency rules
Step 4: Get Project Health Data (deps.dev)
Efficiency rules
Step 5: Find Funding Links
5a: npm funding field (npm ecosystem only)
5b: .github/FUNDING.yml (repo-level, then org-level fallback)
5c: Web search fallback
Efficiency rules
Step 6: Verify Every Link (CRITICAL)
Step 7: Output the Report

Key facts

Author: Plugin author listed as Awesome Copilot Community
License: MIT (LICENSE file of the awesome-copilot repo)
Installs on skills.sh: 8,674 (Nov 2, 2026)
GitHub stars: 40,666 for the whole github/awesome-copilot repo (Nov 2, 2026)
Last repo commit: Oct 30, 2026
What it includes: 1 file: SKILL.md. No scripts
Audits on skills.sh: Gen Agent Trust Hub: pass, Socket: pass, Snyk: pass (Nov 2, 2026)
Part of: The ospo-sponsorship plugin (1 skill listed in plugin.json)
Needs: A GitHub MCP server for get_file_contents, plus web_fetch and web_search tools

What it includes

Starts the workflow for one GitHub repository
Try: “/sponsor expressjs/express”
Runs code · /sponsor owner/repo
Reads the repo's manifest to find the ecosystem, package and version
Looks for package.json, requirements.txt, pyproject.toml, Cargo.toml, go.mod, Gemfile or pom.xml with get_file_contents.
Network · Step 1: Detect ecosystem
Calls the deps.dev GetDependencies endpoint for direct and transitive dependencies
One call per package, so no lockfile parsing.
Network · Step 2: Dependency tree
Calls deps.dev GetVersion for each dependency and reads its source repo
Works in batches of 10 and skips dependencies with no GitHub project.
Network · Step 3: Resolve to GitHub repos
Reads the OSSF Scorecard Maintained score, stars, license and open issues
Score 7 to 10 is labelled actively maintained. The step is optional if rate-limited.
Network · Step 4: Project health
Checks the npm funding field, FUNDING.yml (repo, then owner), then web search
Web search runs for the top 10 unfunded dependencies only.
Network · Step 5: Find funding links
Fetches each funding URL and drops anything not found
Done in batches of 5.
Network · Step 6: Verify every link
Ways to Give Back list, then a Coverage section
Groups by destination and prioritizes GitHub Sponsors.
Step 7: Report

From the official docs

Permissions

Low risk

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

It sends your dependency names to outside services
SKILL.md has the agent call the deps.dev API and the npm registry for each package, fetch every funding URL it finds, and run web searches with package names. Use it on repos whose dependency lists you are happy to look up. github.com
It needs GitHub access through an MCP server
The skill reads files with the GitHub MCP get_file_contents tool, so it can only see what that connection can see. A 404 on a repo is reported as a missing or private repo. github.com
The Copilot plugin route adds one skill
plugin.json for ospo-sponsorship lists this skill and no agents. github.com

Technical details

Talks to	api.deps.dev. registry.npmjs.org. Funding pages found in FUNDING.yml and npm metadata. Web search. GitHub (through the GitHub MCP server)
Scopes	Reads manifest files and FUNDING.yml from GitHub repositories through the GitHub MCP server Fetches deps.dev, npm registry and funding pages Runs web searches for unfunded packages

Questions

What does sponsor-finder do?

It makes your agent scan a GitHub repository's dependencies, direct and transitive, and list the maintainers you can sponsor. Each funding link is fetched and checked before it appears in the report.

How do I install it?

Use the install box at the top of this page. You also need a GitHub MCP server, because the skill reads files with its get_file_contents tool. In GitHub Copilot CLI it comes with the ospo-sponsorship plugin.

How do I run it?

Type /sponsor followed by a GitHub owner/repo, for example /sponsor expressjs/express. SKILL.md also says to run when you give a repository in owner/repo form.

Which package ecosystems does it cover?

The description names npm, PyPI, Cargo, Go, RubyGems, Maven and NuGet. The Step 1 manifest table covers package.json, requirements.txt, pyproject.toml, Cargo.toml, go.mod, Gemfile and pom.xml.

Will it show funding links that do not work?

SKILL.md says never to show an unverified link. It fetches each funding URL, keeps valid pages and drops 404s or not-enrolled pages.

Is it safe?

It bundles no scripts and, per SKILL.md, never clones or shells out. It does send package names to deps.dev, npm and web search, so run it on repos where that is fine.

Does it shame projects without funding?

SKILL.md says to be encouraging, never shaming, and to describe unfunded dependencies as ones that do not have funding set up yet.

Information

updated Nov 2, 2026

Repository: github/awesome-copilot
Folder: skills/sponsor-finder

github/awesome-copilot skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 3

awesome-copilot README · github.com
ospo-sponsorship plugin.json · github.com
sponsor-finder SKILL.md · github.com