Agent skill

Run Coverage

by opensage-agent in opensage-agent/opensage-adk

Run code coverage analysis on a specified file within the sandbox environment.

Apache-2.0Auto-check passedTesting & QA

Install Run Coverage

skills CLI
$ npx skills add opensage-agent/opensage-adk --skill run-coverage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install opensage-agent/opensage-adk run-coverage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/opensage-agent/opensage-adk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/opensage/bash_tools/coverage/run-coverage .claude/skills/run-coverage && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
run-coverage
GitHub stars
127
Token cost
~210 tokens
SKILL.md length
75 words
Files
3 (incl. scripts)
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

Run code coverage analysis on a specified file within the sandbox environment.

  • Tasks that involve Test coverage
  • SKILL.md covers Usage, Parameters, Return Value and Requires Sandbox, plus 1 more section
  • Runs Shell and Python scripts from its folder

What it does

Run Coverage is an agent skill from opensage-agent/opensage-adk. Run code coverage analysis on a specified file within the sandbox environment.

Its SKILL.md is about 210 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `scripts/run_coverage.sh` and `scripts/upload_coverage_to_neo4j.py`).

It sits in Testing & QA, covering Test coverage. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Test coverage

Example prompts

  • “/run-coverage”

Requirements

  • Python 3
  • A Bash shell

What it can do on your machine

Read from SKILL.md and the folder at commit 54d6470. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (Shell and Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Run Coverage loads about 210 tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 75 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~23
When it runs · the whole SKILL.md, loaded when a task matches
~210

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from opensage-agent/opensage-adk at commit 54d6470, republished under its Apache-2.0 licence (© opensage-agent). 75 words, ~210 tokens.

Download SKILL.mdSave it as .claude/skills/run-coverage/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
run-coverage
description
Run code coverage analysis on a specified file within the sandbox environment.
should_run_in_sandbox
coverage
returns_json
false

Run Coverage

Tool to run code coverage analysis on a specified file within the sandbox environment. The testcase_path should be under the /shared directory.

Usage

bash
TARGET_BINARY=/path/to/target /bash_tools/coverage/run-coverage/scripts/run_coverage.sh <testcase_path>

Parameters

testcase_path (required, positional position 0)

Type: str

The absolute path to the testcase file (must be in /shared).

TARGET_BINARY (required, env var)

Type: str

Path to the target binary to run (must be executable).

Return Value

Returns text output with a coverage summary.

Requires Sandbox

coverage

Timeout

240 seconds

© opensage-agent, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in src/opensage/bash_tools/coverage/run-coverage of opensage-agent/opensage-adk.

  • SKILL.md
  • scripts/run_coverage.sh
  • scripts/upload_coverage_to_neo4j.py

Open the folder on GitHubat commit 54d6470

Compare with similar skills

Run Coverage next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Run Coverage compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Run Coverage this skillopensage-agent/opensage-adk127—~210Automated safety check: PassApache-2.0
Requirementsrizsotto/Bear6.5k—~2kAutomated safety check: PassGPL-3.0
Crap Analysisardalis/RiverBooks1352 repos~3.4kAutomated safety check: PassNone
Code Coverages3s-project/s3s311—~789Automated safety check: PassApache-2.0
Project Statusbactopia/bactopia522—~787Automated safety check: PassMIT
Check Coverageldayton/Dippy243—~403Automated safety check: PassMIT

Similar skills

  • Requirements

    rizsotto/Bear

    Write, modify, or review a requirement file under docs/requirements -- pick the single owning file, keep the text contract-only, name IDs so they need no explanation, and verify cross-references and…

    6.5k GitHub stars~2k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Crap Analysis

    ardalis/RiverBooks

    Analyze code coverage and CRAP (Change Risk Anti-Patterns) scores to identify high-risk code.

    135 GitHub starsUsed in 2 repos~3.4k tokens
    Testing & QAAuto-check passed
  • Code Coverage

    s3s-project/s3s

    Measure and grow the line coverage of the s3s crate. An agent skill from s3s-project/s3s.

    311 GitHub stars~789 tokensUpdated today
    Testing & QAAuto-check passed
  • Project Status

    bactopia/bactopia

    Show a live snapshot of the Bactopia project state — component counts, GroovyDoc coverage, nf-test coverage, and structural issues.

    522 GitHub stars~787 tokensUpdated 2 mo ago
    Testing & QAAuto-check passed
  • Check Coverage

    ldayton/Dippy

    Ensure comprehensive test coverage for a CLI handler. An agent skill from ldayton/Dippy.

    243 GitHub stars~403 tokensUpdated 3 mo ago
    Testing & QAAuto-check passed
  • Guarding Destructive Operations

    kajisho5/ffmpeg-skill

    Add and review preconditions on operations that delete, overwrite, rewrite history, or resolve a caller-supplied name to a filesystem path — refusing instead of warning, placing the guard ahead of…

    1.9k GitHub stars~2.6k tokensUpdated 3 days ago
    Testing & QAAuto-check passed

More from opensage-agent/opensage-adk

All 21 skills in this repo
  • Run Fuzzing Campaign

    opensage-agent/opensage-adk

    Run a fuzzing campaign using AFL++ with optional seeds; supports --custommutatorpath (you can write your own custom mutator and use this to execute).

    127 GitHub stars~542 tokensUpdated 2 mo ago
    Auto-check passed
  • Pool

    opensage-agent/opensage-adk

    Run N tasks under a concurrency cap K via a sliding-window worker pool.

    127 GitHub stars~462 tokensUpdated 2 mo ago
    Auto-check passed
  • Create New Tool

    opensage-agent/opensage-adk

    Scaffold a new bashtools Skill under bashtools/newtools/. An agent skill from opensage-agent/opensage-adk.

    127 GitHub stars~302 tokensUpdated 2 mo ago
    Auto-check passed
  • Extract Crashes

    opensage-agent/opensage-adk

    Extract crash inputs from fuzzing output into a target directory.

    127 GitHub stars~215 tokensUpdated 2 mo ago
    Auto-check passed
  • Get Call Paths

    opensage-agent/opensage-adk

    Get a path in the call graph from a source function to a specified destination function in the codebase.

    127 GitHub stars~272 tokensUpdated 2 mo ago
    Auto-check passed
  • Get Callee

    opensage-agent/opensage-adk

    Tool to get the callee of a function in the codebase by function name and file path.

    127 GitHub stars~223 tokensUpdated 2 mo ago
    Auto-check passed

Categories

Questions about Run Coverage

What does Run Coverage do?

Run code coverage analysis on a specified file within the sandbox environment. Run Coverage is an agent skill from opensage-agent/opensage-adk. Run code coverage analysis on a specified file within the sandbox environment.

When should I use Run Coverage?

Run Coverage fits situations like: tasks that involve Test coverage.

How do I install Run Coverage in Claude Code?

Run `npx skills add opensage-agent/opensage-adk --skill run-coverage -a claude-code`. Or copy the skill folder (src/opensage/bash_tools/coverage/run-coverage in opensage-agent/opensage-adk) into .claude/skills/run-coverage in your project. Claude Code loads it when a task matches its description.

How do I install Run Coverage in Codex?

Run `npx skills add opensage-agent/opensage-adk --skill run-coverage -a codex`. Or copy the skill folder (src/opensage/bash_tools/coverage/run-coverage in opensage-agent/opensage-adk) into .agents/skills/run-coverage in your project. Codex loads it when a task matches its description.

Can I use Run Coverage in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add opensage-agent/opensage-adk --skill run-coverage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/run-coverage, .gemini/skills/run-coverage, .github/skills/run-coverage and .opencode/skills/run-coverage in your project.

What does Run Coverage need to run?

Going by SKILL.md and its folder, Run Coverage needs a shell and Python for the scripts in its folder. Our summary lists: Python 3; A Bash shell.

Does Run Coverage access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Run Coverage safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Run Coverage use?

Run Coverage is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Run Coverage use?

About 210 tokens (SKILL.md is roughly 840 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Run Coverage?

Skills that share tags, products or a category with Run Coverage: Requirements (rizsotto/Bear, 6.5k stars), Crap Analysis (ardalis/RiverBooks, 135 stars), Code Coverage (s3s-project/s3s, 311 stars) and Project Status (bactopia/bactopia, 522 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Run Coverage?

opensage-agent (a GitHub organization) maintains it in opensage-agent/opensage-adk, which has 127 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on August 4, 2026.

Source: opensage-agent/opensage-adk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.