examples: Skill for Claude Code

.claude/skills/orchestrate:tests/SKILL.md

orchestrate:tests is a skill for Claude Code from rossoctl/examples. It costs 17 tokens per session (1,109 once invoked), scanned A, original, Apache-2.0.

A workflow for adding a test setup and initial tests to a code repository. Tests are programs that check whether other code behaves as expected.

In plain words
What is it for?
Use it to identify the project's test framework, configure it, find important code paths, write initial tests, and prepare the changes for a pull request.
Why use it?
It creates a safety net before later code-quality and security changes, helping developers detect accidental breakage.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is rossoctl/examples's own configuration. It tells Claude Code how to work on examples itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything examples configures →

Reuse

Borrowing it

Nothing to install: this file belongs to rossoctl/examples. 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/rossoctl/examples/main/.claude/skills/orchestrate:tests/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/rossoctl/examples

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.

agentmods badge for orchestrate:tests

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/rossoctl/examples/orchestrate-tests"><img src="https://agentmods.dev/badge/skills/rossoctl/examples/orchestrate-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,109 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.00017 $0.01109
Opus 5.5 $0.00007 $0.00444
Sonnet 5.5 $0.00003 $0.00222
Haiku 4.5 $0.00002 $0.00111

Measured 1mo ago against content hash fcf5c3ce2b5b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

orchestrate: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 1mo 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/orchestrate:tests/SKILL.md · 153 lines

How it starts

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

flowchart TD
    START(["/orchestrate:tests"]) --> READ["Read plan"]:::orch
    READ --> DETECT["Detect test framework"]:::orch
    DETECT --> CONFIG["Create test config"]:::orch
    CONFIG --> CRITICAL["Identify critical paths"]:::orch
    CRITICAL --> WRITE["Write initial tests"]:::orch
    WRITE --> BRANCH["Create branch"]:::orch
    BRANCH --> SIZE{Under 700 lines?}
    SIZE -->|Yes| PR["Commit + open PR"]:::orch
    SIZE -->|No| SPLIT["Split into sub-PRs"]:::orch
    SPLIT --> PR
    PR --> DONE([Phase complete])

    classDef orch fill:#FF9800,stroke:#333,color:white

Follow this diagram as the workflow.

Orchestrate: Tests

Add test infrastructure and initial test coverage. This is Phase 3 and produces PR #2. Tests come before CI and security — good test coverage is a safety net for the code refactoring that security/quality fixes require.

When to Use

  • After orchestrate:plan identifies tests as a needed phase
  • After precommit phase (linting is the foundation)

Prerequisites

  • Plan exists with tests phase
  • Target repo in .repos/<target>/

Step 1: Detect Test Framework

Marker Language Framework Assertion
pyproject.toml Python pytest built-in assert
go.mod Go testing (stdlib) testify
package.json Node jest or vitest built-in expect
requirements.yml Ansible molecule testinfra

Check existing tests:

find .repos/<target> -type f \( -name "test_*.py" -o -name "*_test.go" -o -name "*.test.*" \) 2>/dev/null

Step 2: Create Test Configuration

Python

  • tests/conftest.py — shared fixtures
  • tests/__init__.py — package marker
  • pyproject.toml — add [tool.pytest.ini_options] with testpaths = ["tests"]

Go

  • *_test.go files alongside source
  • testdata/ for fixtures
  • internal/testutil/ for shared helpers

Node

  • jest.config.ts or vitest.config.ts at root
  • __tests__/ directory or *.test.ts alongside source

Read the full file on GitHub · 153 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. 1mo ago First seen · 153 lines · 17 tokens per session scan A fcf5c3ce2b5b

Subscribe to this mod's changes

orchestrate:tests is a skill published in the GitHub repository rossoctl/examples (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 17 tokens to every session and 1,109 once invoked, about $0.0001 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-08-30.

Related

Other skills, from other repositories

testing-patterns

Redirect — testing-patterns was split into 5 focused sub-skills. Use when looking for testing-patterns, writing tests, or test automation. Redirects to testing-unit, testing-e2e, testing-integration, testing-llm, or testing-perf.

yonatangross/orchestkit · 59 tokens

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens