oss-write-tests

oss-write-tests is a skill for Claude Code, Codex from chiruu12/OSS-Skills. It costs 83 tokens per session (2,527 once invoked), scanned A, original, MIT.

A workflow for adding tests to untested code in an open-source software repository. It studies the repository's existing test style and helps write tests that fit it.

In plain words
What is it for?
Use it when making a first contribution, testing previously uncovered code, or learning a codebase through its behavior. It is not for tests written as part of a bug fix.
Why use it?
It helps contributors find coverage gaps and reduce the risk of adding tests that conflict with the project's conventions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when making a first contribution, testing previously uncovered code, or learning a codebase through its behavior. It is not for tests written as part of a bug fix.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chiruu12/oss-skills/oss-write-tests
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 chiruu12/OSS-Skills --skill oss-write-tests
Clone the repo
git clone --depth 1 https://github.com/chiruu12/OSS-Skills

Made for: Claude Code, Codex.

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 oss-write-tests

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/chiruu12/oss-skills/oss-write-tests"><img src="https://agentmods.dev/badge/skills/chiruu12/oss-skills/oss-write-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,527 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00083 $0.02527
Opus 5 $0.00042 $0.01264
Sonnet 5 $0.00017 $0.00505
Haiku 4.5 $0.00008 $0.00253

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

Security

Grade A, and why

oss-write-tests 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.

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.

skills/oss-write-tests/SKILL.md · 234 lines

How it starts

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

Write Tests

Add tests for untested code — the highest-value, lowest-risk first contribution. You need to understand the code deeply without modifying it, and the result is almost always welcome.

Purpose

Test contributions teach you a codebase faster than any other contribution type. You read every function signature, trace every code path, and understand every edge case — without the pressure of changing production code. Maintainers love test PRs because they reduce risk for everyone. This skill guides you through finding untested code, learning the repo's test conventions, and writing tests that a maintainer would write themselves.

When to Use

  • Making your first contribution to a repo and want something low-risk
  • You've found code with no tests or poor coverage
  • You want to learn a codebase deeply before tackling a bug or feature
  • NOT when writing tests as part of a bug fix — use oss-contribute for that
  • NOT when the repo has no test infrastructure at all — that's a different conversation with maintainers

Prerequisites

  • Repo forked, cloned, and set up (from oss-prep-to-contribute)
  • Test suite runs successfully (make test, npm test, pytest, etc.)
  • User has a target module or area in mind

Process

1. Identify untested code

Find code that lacks test coverage. Use multiple signals — don't rely on just one.

# Check if the repo has coverage reports
ls coverage/ htmlcov/ .coverage *.lcov 2>/dev/null

# Find source files without corresponding test files
# Adapt the pattern to the repo's naming convention
find src/ -name "*.ts" | while read f; do
  test_file=$(echo "$f" | sed 's|src/|tests/|; s|\.ts$|.test.ts|')
  [ ! -f "$test_file" ] && echo "No tests: $f"
done

# Find public functions without any test assertions
grep -rn "export function\|def \|pub fn\|func " src/ --include="*.ts" --include="*.py" --include="*.rs" --include="*.go" | head -30

Then cross-reference against test files:

# What symbols are already tested?
grep -rn "describe\|it(\|test(\|def test_\|func Test" tests/ test/ __tests__/ spec/ | head -30

Read the full file on GitHub · 234 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. 9d ago First seen · 234 lines · 83 tokens per session scan A 42573c86a37f

Subscribe to this mod's changes

oss-write-tests is a skill published in the GitHub repository chiruu12/OSS-Skills (62 stars, last pushed 15d ago), licensed MIT. It adds 83 tokens to every session and 2,527 once invoked, about $0.0004 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-30.

Related

Other skills, from other repositories

056-design-avoid-breaking-changes

Use when you need to review a plan, OpenSpec change, specification, or implementation proposal for breaking-change risk across commands, skills, generated outputs, XML sources, README/docs, tests, CI, APIs, schemas, configuration, data, migration, and release guidance. This should trigger for requests such as Review…

jabrena/plinth · 106 tokens

workflow

Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.

claude-world/director-mode-lite · 52 tokens

done

End-of-session shipping gate — "prove it works, then ship it." Runs an evidence checklist (full test suite, lint/typecheck, build, and actually running the change — output quoted, never asserted), then a fresh-context two-stage review by a sub-agent that sees only the diff and the spec: spec-compliance first…

duthaho/skillhub · 204 tokens

ui-visual-regression

Automates visual regression testing for DB Console UI changes. Compares screenshots and network requests between the current branch and its merge base using roachprod, playwright-cli, and ImageMagick. Use when the user wants to verify UI changes haven't introduced visual or behavioral regressions.

cockroachdb/cockroach · 61 tokens

dev-cycle

· Run dev workflow: branch, implement, lint/test, review, docs, PR, merge, release. Triggers: 'start working', 'kick off', 'wrap up', 'ship this', 'ready to ship'. Not for single git ops (use git).

iuliandita/skills · 58 tokens

release

Release preparation workflow - security audit → E2E tests → review → changelog → docs.

parcadei/Continuous-Claude-v3 · 20 tokens