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.
npx skills add bdfinst/agentic-dev-team --skill test-improvegit clone --depth 1 https://github.com/bdfinst/agentic-dev-teamWrote 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/skills/bdfinst/agentic-dev-team/test-improve)<a href="https://agentmods.dev/skills/bdfinst/agentic-dev-team/test-improve"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/test-improve/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/skills/bdfinst/agentic-dev-team/test-improve"><img src="https://agentmods.dev/badge/skills/bdfinst/agentic-dev-team/test-improve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 166 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00119 | $0.03245 |
| Opus 5.5 | $0.00048 | $0.01298 |
| Sonnet 5.5 | $0.00024 | $0.00649 |
| Haiku 4.5 | $0.00012 | $0.00325 |
Grade A, and why
test-improve 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.
How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Improve
Role: orchestrator. This command sequences existing skills and agents through a
ten-phase (0-9) analyze-then-improve workflow; it does not implement, audit, or
write tests itself. Each phase is delegated to the worker skill or agent
that owns it, and per-phase progress is persisted to
.claude/memory/test-improve/<slug>/phase-<n>.md so /continue (and --from-phase)
can resume.
You have been invoked with the /test-improve command.
Orchestrator constraints
- Delegate every phase. Call the owning skill or agent (
/test-health,/gherkin-derive,/issues-from-assessment,/build,/coverage-baseline,/coverage-delta,/mutation-testing,mutation-killagent,/quality-targets-converge,/test-design,/code-review,/apply-fixes). Never re-implement their logic here. - Honor the human gates. Do not advance past a gate without explicit approval.
- Confirm the approach first. Phase 0 owns the approach contract; do not start work until it has completed and its answers are persisted.
- Baseline before changing anything. Coverage (and mutation, when
enabled) must land directly in
.dev-team-reports/test-improve/<slug>/data/before any file under the stack's test directory is modified. - Be concise. Report each phase's outcome and the next gate, nothing more.
Parse Arguments
- Positional:
<repo-path>(default: cwd). --parent <url>— optional tracker parent issue URL; the host selects the CLI (ADO / GitHub / GitLab / Jira). Omit for local-files mode (the default), which writes to.dev-team-reports/test-improve/and.claude/plans/test-improve/.--analyze-only— run Phase 0 then Phase 1 directly and exit after Phase 1 with a summary of the improvement plan (bypassing the default Baseline/Derive-Gherkin ordering — see Phase 0's--analyze-onlysemantics). No baseline is captured; no code changes.--from-phase [<n>]— skips completed phases and resumes at phasenwhen.claude/memory/test-improve/<slug>/phase-<n-1>.mdexists. The number is optional. Passed with no argument,/test-improveauto-detects the resume point from.claude/memory/test-improve/<slug>/(seereferences/phase-0-approach-contract.md): it resumes at the phase after the highest completed progress file and prints which phase it resolved to and why. An explicit<n>overrides auto-detection. Either form does not re-prompt Phase-0 inputs; to change them, delete.claude/memory/test-improve/<slug>/phase-0.mdand re-run from Phase 0.--stack <id>— force a stack profile (e.g.js,dotnet,java,go) when manifest detection is ambiguous.
What ships with it
13 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/phase-0-approach-contract.md 14 KB
- references/phase-1-analyze.md 8.5 KB
- references/phase-2-baseline.md 8.2 KB
- references/phase-3-derive-gherkin.md 3.2 KB
- references/phase-4-plan-fixes.md 2.8 KB
- references/phase-5-improve.md 13 KB
- references/phase-6-refactor-decision.md 2.6 KB
- references/phase-7-refactor.md 2.8 KB
- references/phase-8-validate.md 4.2 KB
- references/phase-9-close-out-prompt.md 1.3 KB
- references/phase-9-report.md 3.6 KB
- references/review-loop.md 5.6 KB
- templates/executive-summary.md 5.4 KB
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.
- 1mo ago First seen · 240 lines · 119 tokens per session scan A 8f14a68018a0
test-improve is a skill published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 119 tokens to every session and 3,245 once invoked, about $0.0005 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-09-05.
Other skills, from other repositories
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.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
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".
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.
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.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.