DQIII8: Skill for Claude Code

.claude/skills/test-team/SKILL.md

test-team is a skill for Claude Code from senda-labs/DQIII8. It costs 35 tokens per session (526 once invoked), scanned A, original, MIT.

A test setup for coordinating two coding agents in sequence: one researches the Kelly Criterion, a formula for deciding investment size, and another implements it in Python.

In plain words
What is it for?
Use it to verify agent-team handoffs, including producing a research file and then building a validated, typed Kelly Criterion function with an optional Half-Kelly setting.
Why use it?
It tests whether research from one agent can be passed directly to another agent for implementation.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

This is senda-labs/DQIII8's own configuration. It tells Claude Code how to work on DQIII8 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 DQIII8 configures →

Part of the dqiii8 plugin — 22 skills, 14 commands, 17 agents shipped together

Reuse

Borrowing it

Nothing to install: this file belongs to senda-labs/DQIII8. 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/senda-labs/DQIII8/main/.claude/skills/test-team/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/senda-labs/DQIII8

Made for: Claude Code.

Or install dqiii8, the plugin that ships this one along with the rest of its 22 skills, 14 commands, 17 agents.

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 test-team

README.md
[![agentmods](https://agentmods.dev/badge/skills/senda-labs/dqiii8/test-team/github.svg)](https://agentmods.dev/skills/senda-labs/dqiii8/test-team)
Your own site
<a href="https://agentmods.dev/skills/senda-labs/dqiii8/test-team"><img src="https://agentmods.dev/badge/skills/senda-labs/dqiii8/test-team/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 test-team

Your own site · 80×15
<a href="https://agentmods.dev/skills/senda-labs/dqiii8/test-team"><img src="https://agentmods.dev/badge/skills/senda-labs/dqiii8/test-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 526 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.00526
Opus 5 $0.00017 $0.00263
Sonnet 5 $0.00007 $0.00105
Haiku 4.5 $0.00003 $0.00053

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

Security

Grade A, and why

test-team 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 12d 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/test-team/SKILL.md · 69 lines

How it starts

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

/test-team — Agent Team Coordination Test

Direct coordination test between agents using Agent Teams. Demonstrates that the output of one agent feeds directly into the next.

Team

Task: Implement Kelly Criterion in Python based on prior research.

Agent 1 — research-analyst (first)

Researches the Kelly Criterion and produces a structured summary with:

  • Exact mathematical formula: f* = (bp - q) / b where b = net odds, p = win probability, q = 1 - p
  • Input parameters and their valid ranges
  • Half-Kelly variant (f* / 2) and when to prefer it
  • Use cases in systematic trading (position sizing)
  • Known limitations (sensitivity to p estimation)

Writes result to: tasks/results/research-kelly-[timestamp].md

Agent 2 — python-specialist (after Agent 1)

Reads the research-analyst result from tasks/results/research-kelly-*.md and based on it implements:

def kelly_criterion(win_prob: float, win_loss_ratio: float, half_kelly: bool = True) -> float:
    """
    Calculates the optimal position size according to Kelly Criterion.
    ...
    """

Implementation requirements:

  • Full type hints
  • Input validation (0 < win_prob < 1, win_loss_ratio > 0)
  • Half-Kelly support (default True — more conservative)
  • Usage example in docstring with real trading values

Writes result to: tasks/results/python-kelly-[timestamp].md

Coordination protocol

research-analyst → tasks/results/research-kelly-*.md
                              ↓
python-specialist reads that file → implements function

The python-specialist does NOT start until research-analyst has written its result. This validates sequential coordination of Agent Teams.

Execution

Launch both agents as a coordinated team. The orchestrator waits for the result from research-analyst before passing context to python-specialist. When done, show:

  1. Research summary (formula + parameters)
  2. Implemented Python code
  3. Confirmation: [TEAM] Kelly Criterion — research + impl complete

Read the full file on GitHub · 69 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. 12d ago First seen · 69 lines · 35 tokens per session scan A 12a8509f1a3a

Subscribe to this mod's changes

test-team is a skill published in the GitHub repository senda-labs/DQIII8 (11 stars, last pushed 23d ago), licensed MIT. It adds 35 tokens to every session and 526 once invoked, about $0.0002 per session on Opus 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.