An open-source research workflow for finding contribution opportunities in active, popular code repositories. It looks for issues such as “help wanted” and “good first issue,” then prepares a plan for contributing.

Use it to find bug fixes or feature work in trending repositories and prepare contribution dossiers for potential pull requests.

It removes the effort of searching many repositories and judging which issues are realistic and worthwhile. It helps turn a vague interest in contributing into a concrete candidate task.

oss-hunter — Skill for Claude Code by ratnesh-maurya

Install

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.

Any agent

npx skills add ratnesh-maurya/cursor-claude-personas --skill oss-hunter

Clone the repo

git clone --depth 1 https://github.com/ratnesh-maurya/cursor-claude-personas

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ratnesh-maurya/cursor-claude-personas/oss-hunter/github.svg)](https://agentmods.dev/skills/ratnesh-maurya/cursor-claude-personas/oss-hunter)

Your own site

<a href="https://agentmods.dev/skills/ratnesh-maurya/cursor-claude-personas/oss-hunter"><img src="https://agentmods.dev/badge/skills/ratnesh-maurya/cursor-claude-personas/oss-hunter/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ratnesh-maurya/cursor-claude-personas/oss-hunter"><img src="https://agentmods.dev/badge/skills/ratnesh-maurya/cursor-claude-personas/oss-hunter.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 617 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00016	$0.00617
Opus 5	$0.00008	$0.00309
Sonnet 5	$0.00003	$0.00123
Haiku 4.5	$0.00002	$0.00062

Measured 9d ago against content hash 3c992361d834, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

oss-hunter 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.

The scan reads SKILL.md. This mod also ships 1 executable file (bin/hunter.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

.claude/skills/oss-hunter/SKILL.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OSS Hunter 🎯

A precision skill for agents to find, analyze, and strategize for high-impact Open Source contributions. This skill helps you become a top-tier contributor by identifying the most "mergeable" and influential issues in trending repositories.

When to Use

Use when the user asks to find open source issues to work on.
Use when searching for "help wanted" or "good first issue" tasks in specific domains like AI or Web3.
Use to generate a "Contribution Dossier" with ready-to-execute strategies for trending projects.

Quick Start

Ask your agent:

"Find me some help-wanted issues in trending AI repositories."
"Hunt for bug fixes in langchain-ai/langchain that are suitable for a quick PR."
"Generate a contribution dossier for the most recent trending projects on GitHub."

Workflow

When hunting for contributions, the agent follows this multi-stage protocol:

Phase 1: Repository Discovery

Use web_search or gh api to find trending repositories. Focus on:

Stars > 1000
Recent activity (pushed within 24 hours)
Relevant topics (AI, Agentic, Web3, Tooling)

Phase 2: Issue Extraction

Search for specific labels:

help-wanted
good-first-issue
bug
v1 / roadmap

gh issue list --repo owner/repo --label "help wanted" --limit 10

Phase 3: Feasibility Analysis

Analyze the issue:

Reproducibility: Is there a code snippet to reproduce the bug?
Impact: How many users does this affect?
Mergeability: Check recent PR history. Does the maintainer merge community PRs quickly?
Complexity: Can this be solved by an agent with the current tools?

Phase 4: The Dossier

Generate a structured report for the human:

Project Name & Stars
Issue Link & Description
Root Cause Analysis (based on code inspection)
Proposed Fix Strategy
Confidence Score (1-10)

Limitations

Accuracy depends on the availability of gh CLI or web_search tools.
Analysis is limited by context window when reading very large repositories.
Cannot guarantee PR acceptance (maintainer discretion).

Read the full file on GitHub · 76 lines

Files

What ships with it

1 file 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.

bin/hunter.py 1.9 KB runs code

Changes

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 · 76 lines · 16 tokens per session scan A 3c992361d834

Subscribe to this mod's changes

oss-hunter is a skill published in the GitHub repository ratnesh-maurya/cursor-claude-personas (8 stars, last pushed 5mo ago), licensed MIT. It adds 16 tokens to every session and 617 once invoked, about $0.0001 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.

Git and workflow Research ai-personas anthropic-claude code-assistant cursor developer-tools ide-configuration

gentle-ai-collab-perfect

Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…

Gentleman-Programming/gentle-ai · 106 tokens

branch-pr

Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.

Gentleman-Programming/gentle-ai · 26 tokens

work-unit-commits

Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.

Gentleman-Programming/gentle-ai · 33 tokens

github-release-briefing-skill

Create a source-linked briefing for the latest published GitHub release of a public repository. Use for engineering teams tracking a dependency release; do not use it to publish releases or change repositories.

FrancyJGLisboa/agent-skill-creator · 45 tokens

ijfw-ship

Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…

FerroxLabs/ijfw · 139 tokens

ijfw-commit

Terse conventional commits. Trigger: commit, git commit, /ijfw-commit.

FerroxLabs/ijfw · 22 tokens