agentmods.dev

contribute

contribute is a skill for Claude Code from tobihagemann/turbo. It costs 43 tokens per session (735 once invoked), scanned A, original, MIT.

A workflow for proposing improvements to the project's coding-agent skills as GitHub issues.

In plain words
What is it for?
It is for comparing proposed changes with the upstream skills, choosing which to submit, and drafting contribution issues.
Why use it?
It turns lessons from development sessions into clearly reviewed suggestions for maintainers.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: names the AskUserQuestion tool.

Part of the turbo plugin — 71 skills shipped together

not rated 420repo +1 today A scan 43 tokens original MIT

Good fit It is for comparing proposed changes with the upstream skills, choosing which to submit, and drafting contribution issues.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tobihagemann/turbo/contribute
View source ↗ tobihagemann/turbo
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 tobihagemann/turbo --skill contribute
Clone the repo
git clone --depth 1 https://github.com/tobihagemann/turbo

Made for: Claude Code.

Or install turbo, the plugin that ships this one along with the rest of its 71 skills.

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.

agentmods badge for contribute

README.md
[![agentmods](https://agentmods.dev/badge/skills/tobihagemann/turbo/contribute/github.svg)](https://agentmods.dev/skills/tobihagemann/turbo/contribute)
Your own site
<a href="https://agentmods.dev/skills/tobihagemann/turbo/contribute"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/contribute/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.

agentmods 80×15 button for contribute

Your own site · 80×15
<a href="https://agentmods.dev/skills/tobihagemann/turbo/contribute"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/contribute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 735 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.00735
Opus 5.5 $0.00017 $0.00294
Sonnet 5.5 $0.00009 $0.00147
Haiku 4.5 $0.00004 $0.00073

Measured 3d ago against content hash 8e7f9b65a883, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

contribute 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 3d 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.

claude/skills/contribute/SKILL.md · 69 lines

How it starts

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

Contribute

Propose an improvement to a turbo skill as an issue on tobihagemann/turbo.

Step 1: Identify the Proposed Change

Take the proposed changes from the lessons passed in: each names the turbo skill it targets, the change, and the session evidence behind it. Without them, take the proposed changes from conversation context. When neither describes a change to a turbo skill, tell the user there is nothing to contribute and stop.

Read each target skill's current text upstream, so each change is stated against the file as it stands on main:

gh api repos/tobihagemann/turbo/contents/claude/skills/<name>/SKILL.md -H 'Accept: application/vnd.github.raw'

Leave out a change whose target skill does not exist upstream, and tell the user.

Present the changes in a summary table:

| # | Skill | Change Summary |
|---|-------|----------------|
| 1 | /evaluate-findings | Added handling for security-default findings |
| 2 | /self-improve | Clarified routing for trusted reviewer feedback |

Use AskUserQuestion to confirm which changes to propose.

Step 2: Craft Contribution Context

For each change, construct a "why" explanation. The goal: the turbo maintainer should understand what happened and why the existing instructions were insufficient, without learning anything about the contributor's project.

Use this template:

During [general workflow description], the skill's instructions [what was missing or wrong]. This caused [what happened]. The change [what it does] so that [benefit].

Example:

During a code review session, the evaluate-findings skill encountered a finding with security-default severity. The existing instructions only handled critical, high, medium, and low severities, causing the finding to be silently dropped. The change adds security-default to the severity handling table so these findings are properly triaged.

The maintainer implements the change, so state it concretely alongside the "why": the file path under claude/skills/<name>/, the step or section it belongs in, and the exact replacement text or a diff.

Read the full file on GitHub · 69 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.

  1. 3d ago First seen · 69 lines · 43 tokens per session scan A 8e7f9b65a883

Subscribe to this mod's changes

contribute is a skill published in the GitHub repository tobihagemann/turbo (420 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 735 once invoked, about $0.0002 per session on Opus 5.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-11-09.

Building agentsClaude Codeagent-skillsclaude-skillscodexdeveloper-toolsskills
Related

contribute compared with skills from other repositories

contribute next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
contributetobihagemann/turboSkill420todayMITA43Claude Code
offensive-c2-frameworksSnailSploit/Claude-RedSkill11kyesterdayMITA250Claude Code, Codex
offensive-crypto-attacksSnailSploit/Claude-RedSkill11kyesterdayMITA261Claude Code, Codex
offensive-parameter-pollutionSnailSploit/Claude-RedSkill11kyesterdayMITA0Claude Code, Codex
offensive-z-waveSnailSploit/Claude-RedSkill11kyesterdayMITA113Claude Code, Codex
fiscalisteromainsimon/paperasseSkill2.6ktodayMITA306Claude Code
comptableromainsimon/paperasseSkill2.6ktodayMITA248Claude Code