Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/yonatangross/orchestkitnpx agentmods add commands/yonatangross/orchestkit/coverWrote 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.
[](https://agentmods.dev/commands/yonatangross/orchestkit/cover)<a href="https://agentmods.dev/commands/yonatangross/orchestkit/cover"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/cover/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.
<a href="https://agentmods.dev/commands/yonatangross/orchestkit/cover"><img src="https://agentmods.dev/badge/commands/yonatangross/orchestkit/cover.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00095 | $0.05941 |
| Opus 5.5 | $0.00038 | $0.02376 |
| Sonnet 5.5 | $0.00019 | $0.01188 |
| Haiku 4.5 | $0.00010 | $0.00594 |
Grade B, and why
cover scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
> `.claude/settings.json` or `~/.claude/settings.json`, CC's default `"fresh"` How it starts
The opening of the file, as written. The whole thing — 471 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-generated from skills/cover/SKILL.md
Source: https://github.com/yonatangross/orchestkit
Cover: Test Suite Generator
Host-neutral workflow. Invoke by skill name (cover). Claude Code slash routing, YAML hook loaders, and .claude/chain live in skills/cover/references/claude-code.md.
Generate comprehensive test suites for existing code with real-service integration testing and automated failure healing.
Note: If
disableSkillShellExecutionis enabled (CC 2.1.91), the precondition check for vitest/jest won't run. Verify a test runner is installed before proceeding:npx vitest --versionornpx jest --version.
Quick Start
cover authentication flow
cover --model=opus payment processing
cover --tier=unit,integration user service
cover --real-services checkout pipeline
Argument Resolution
A pronoun target (this, them, the above) is read back from the conversation, announced in one line, and used: Read("../../shared/rules/target-resolution.md"), inline half.
SCOPE = "$ARGUMENTS" # e.g., "authentication flow"
# Flag parsing
MODEL_OVERRIDE = None
TIERS = ["unit", "integration", "e2e"] # default: all three
REAL_SERVICES = False
for token in "$ARGUMENTS".split():
if token.startswith("--model="):
MODEL_OVERRIDE = token.split("=", 1)[1]
SCOPE = SCOPE.replace(token, "").strip()
elif token.startswith("--tier="):
TIERS = token.split("=", 1)[1].split(",")
SCOPE = SCOPE.replace(token, "").strip()
elif token == "--real-services":
REAL_SERVICES = True
SCOPE = SCOPE.replace(token, "").strip()
Step -0.5: Effort-Aware Coverage Scaling (CC 2.1.76, env var since 2.1.120)
Read $CLAUDE_EFFORT (CC 2.1.120+) first; explicit --effort= token wins as override. Default high when CC < 2.1.120 and no flag. Pattern matches assess + explore (#1540). Scale test generation depth:
| Effort Level | Tiers Generated | Agents | maxIterations to pass Phase 5 |
|---|---|---|---|
| low | Unit only | 1 agent | 2 (1 repair + 1 verify) |
| medium | Unit + Integration | 2 agents | 2 (1 repair + 1 verify) |
| high (default) | Unit + Integration + E2E | 3 agents | 3 (2 repairs + 1 verify) |
| xhigh (CC 2.1.111+) | Unit + Integration + E2E | 3 agents | 3 (the ceiling; xhigh adds agents, not heal passes) |
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 Changed · +2 lines 78063df92700
- 20d ago Changed ca1459224748
- 24d ago Changed · +3 lines fb33261c5d0b
- 26d ago Changed · +2 lines fa4658d2b7de
- 1mo ago Changed · +2 lines 3bcf598c89c2
- 1mo ago Changed 796e4edb359d
- 1mo ago First seen · 462 lines · 95 tokens per session scan B f6c0ad875776
cover is a command published in the GitHub repository yonatangross/orchestkit (297 stars, last pushed today), licensed MIT. It adds 95 tokens to every session and 5,941 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
verify
You are invoking the verify skill - comprehensive verification following Boris Cherny's pattern.
mockless-tests-block
When this command is used, use the following block. Acknowledge your understanding and then await the user's request.
generate-tests
Comprehensive test suite generation with unit, integration, and end-to-end tests. Analyzes existing code patterns and generates thorough test coverage following testing best practices and project conventions.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.