What is ds-improve-test-coverage?

A command for adding automated tests around code changed in the current branch, with a stated goal of at least 95% coverage.

Use it to inspect staged or branch changes, add tests following the project's patterns, and run pytest to check that they pass.

It finds changed code that existing tests do not exercise, including error paths and alternate branches.

How rossumai/rossum-agents configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to rossumai/rossum-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/rossumai/rossum-agents/master/.claude/commands/ds-improve-test-coverage.md

Clone the repo

git clone --depth 1 https://github.com/rossumai/rossum-agents

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/commands/rossumai/rossum-agents/ds-improve-test-coverage.svg)](https://agentmods.dev/commands/rossumai/rossum-agents/ds-improve-test-coverage)

Your own site

<a href="https://agentmods.dev/commands/rossumai/rossum-agents/ds-improve-test-coverage"><img src="https://agentmods.dev/badge/commands/rossumai/rossum-agents/ds-improve-test-coverage.svg" alt="Measured on agentmods" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 366 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.00000	$0.00366
Opus 5	$0.00000	$0.00183
Sonnet 5	$0.00000	$0.00073
Haiku 4.5	$0.00000	$0.00037

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

Security

Grade A, and why

ds-improve-test-coverage 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 8d 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/commands/ds-improve-test-coverage.md · 60 lines

What it actually says

Improve Test Coverage

Goal: Add tests for code changed in the current branch to achieve 95%+ coverage.

Scope

Context	What to Cover
Staged changes	`git diff --cached`
Branch changes	`git diff master...HEAD` if no staged changes

Coverage Priorities

Priority	Target
High	New functions and methods
High	Modified logic branches
Medium	Error handling paths
Low	Simple property accessors

Approach

Step	Action
Identify	List new/modified functions from diff
Analyze	Check existing test coverage for each
Plan	Propose tests for uncovered code using `AskUserQuestion`
Write	Add tests following existing test patterns
Verify	Run `pytest` to confirm tests pass

Test Standards

Rule	Implementation
Location	Mirror source structure in `tests/`
Naming	`test_<function_name>` or `Test<ClassName>`
Fixtures	Reuse from `conftest.py` where available
Assertions	One logical assertion per test
Mocking	Mock external dependencies, not internal logic

Output

Report summary as:

## Tests Added

- `test_file.py::test_function_name` - covers <description>
- ...

Coverage: <N> new tests, <N> functions covered

Constraints

Ask before writing tests (use AskUserQuestion to confirm plan)
Follow existing test patterns in the codebase
No tests for trivial code (simple getters, pass-through calls)
Run pytest after adding tests to verify they pass

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.

8d ago First seen · 60 lines · 0 tokens per session scan A 0e43b9fe601e

Subscribe to this mod's changes

ds-improve-test-coverage is a command published in the GitHub repository rossumai/rossum-agents (11 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 366 tokens. 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.

Testing

verify

Run repository verification using the verification-loop skill.

cloudnative-co/claude-code-starter-kit · 9 tokens

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

rossum-agents: Command for Claude Code