A workflow for contributing code to an open-source project from a fork. A fork is your copy of another repository, while the upstream repository is the original project.

Use it to sync a fork, read contribution and licensing requirements, create a feature branch, match the project’s coding and testing style, and prepare a pull request.

It reduces mistakes caused by working from an outdated fork, ignoring the project’s contribution rules, or formatting changes differently from the rest of the project.

oss-contrib — Skill for Claude Code by Sagargupta16

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 Sagargupta16/claude-skills --skill oss-contrib

Clone the repo

git clone --depth 1 https://github.com/Sagargupta16/claude-skills

Made for: Claude Code.

Or install oss-contrib, the plugin that ships this one along with the rest of its 1 skill, 2 commands, 1 agent.

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/sagargupta16/claude-skills/oss-contrib/github.svg)](https://agentmods.dev/skills/sagargupta16/claude-skills/oss-contrib)

Your own site

<a href="https://agentmods.dev/skills/sagargupta16/claude-skills/oss-contrib"><img src="https://agentmods.dev/badge/skills/sagargupta16/claude-skills/oss-contrib/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/sagargupta16/claude-skills/oss-contrib"><img src="https://agentmods.dev/badge/skills/sagargupta16/claude-skills/oss-contrib.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,202 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.00052	$0.01202
Opus 5	$0.00026	$0.00601
Sonnet 5	$0.00010	$0.00240
Haiku 4.5	$0.00005	$0.00120

Measured 11d ago against content hash 740f0778b053, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

oss-contrib 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 11d 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.

plugins/oss-contrib/skills/oss-contrib/SKILL.md · 143 lines

How it starts

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

Open Source Contribution Workflow

Quick Reference

Step	Action
1. Sync	`git fetch upstream && git merge upstream/main`
2. Research	Read CONTRIBUTING.md, PR templates, CLA requirements
3. Branch	Create feature branch from synced default branch
4. Code	Match upstream style exactly - no personal preferences
5. Test	Run upstream's test suite, match their test patterns
6. PR	Follow their PR template, fill all required fields

Pre-Contribution Checklist

Before writing any code:

Sync fork with upstream

git fetch upstream
git checkout main
git merge upstream/main
git push origin main

Read contribution guide
- CONTRIBUTING.md in repo root
- .github/PULL_REQUEST_TEMPLATE.md
- CLA/DCO signing requirements
- Required CI checks and labels
Create feature branch
```
git checkout -b fix/issue-description
```
Scope the change
- Only modify files directly related to the issue
- Never refactor or "improve" unrelated code
- Never add features beyond what was requested

Code Style Matching

The most important rule: match the upstream project's style exactly.

Before writing code, check:

Indentation (spaces vs tabs, 2 vs 4)
Quote style (single vs double)
Import ordering and grouping
Naming conventions (snake_case vs camelCase)
Test patterns and fixtures
Docstring format (Google, NumPy, Sphinx)
Error handling patterns
Linter/formatter config (.editorconfig, pyproject.toml, .eslintrc)

Do NOT apply personal preferences. Do NOT run your own formatters unless they match upstream's config.

PR Best Practices

Title: Match upstream convention (check recent merged PRs for format)
Description: Fill every section of their PR template
Commits: Squash to clean history if they prefer, keep atomic if they prefer
Tests: Always include tests - match their test patterns exactly
Scope: One logical change per PR
CI: Ensure all required checks pass before requesting review

Read the full file on GitHub · 143 lines

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.

11d ago First seen · 143 lines · 52 tokens per session scan A 740f0778b053

Subscribe to this mod's changes

oss-contrib is a skill published in the GitHub repository Sagargupta16/claude-skills (5 stars, last pushed 5d ago), licensed MIT. It adds 52 tokens to every session and 1,202 once invoked, about $0.0003 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.

Claude Code Code review Git and workflow ai-agents claude developer-tools marketplace plugins

issue-analyzing

Use this skill when the user asks to analyze a specific GitHub issue, understand what area of code an issue affects, assess an issue's scope, or research the code context around an issue — example triggers like "analyze issue.

shopwareLabs/ai-coding-tools · 51 tokens

review-pr

Review a Pull Request in one of two postures: an expository "tour guide" that walks through changes in logical order, or an adversarial audit that assumes the change is wrong until proven safe and hunts for the failure mode. Triggers: "review PR #123", "adversarial review", "walk me through this PR", "PR tour guide"…

jontsai/claude-plugins · 139 tokens

release

This skill should be used when the user wants to create a new release — bump version, tag, push, create GitHub release, and optionally publish to npm. Use when user says "release", "bump version", "publish", "cut a release", or "release candidate".

NikiforovAll/claude-code-marketplace · 60 tokens

cut-release

Prepare and publish an explicitly requested Foundry plugin-edition release using its actual platform branch, version owner and catalog. Includes coordinated README and verification gates; never an automatic release trigger.

V-Songbird/foundry · 39 tokens

coordinate-readmes

Coordinate a Foundry plugin's Claude and Codex README editions, preserving common product content and verifying platform-specific installation, availability and benchmark evidence. Use for paired README edits, benchmark updates or a README parity review before release.

V-Songbird/foundry · 48 tokens

team-workspace

Set up or work with a git-backed team workspace for co-owned artifacts — charters, strategy docs, decision records — separate from private reflections. Triggers: "share our team charter with the team", "set up a shared haku workspace", "put our strategy doc in the team repo", "how do teams use haku together".…

shrwnsan/vibekit-claude-plugins · 0 tokens