datris-platform-oss: Command for Claude Code

.claude/commands/lead.md

lead is a command for Claude Code from datris/datris-platform-oss. It costs 26 tokens per session (887 once invoked), scanned A, original, Apache-2.0.

A command that coordinates one software story from a branch through implementation, review, end-to-end testing, and optionally release.

In plain words
What is it for?
Use it to run a story through tester specifications, implementation, review fixes, end-to-end testing, and optional release work.
Why use it?
It provides a defined handoff between the people or agents who write tests, implement changes, review code, test the complete flow, and release it.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: mentions Claude Code.

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

Reuse

Borrowing it

Nothing to install: this file belongs to datris/datris-platform-oss. 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/datris/datris-platform-oss/main/.claude/commands/lead.md
Clone the repo
git clone --depth 1 https://github.com/datris/datris-platform-oss

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 lead

README.md
[![agentmods](https://agentmods.dev/badge/commands/datris/datris-platform-oss/lead/github.svg)](https://agentmods.dev/commands/datris/datris-platform-oss/lead)
Your own site
<a href="https://agentmods.dev/commands/datris/datris-platform-oss/lead"><img src="https://agentmods.dev/badge/commands/datris/datris-platform-oss/lead/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 lead

Your own site · 80×15
<a href="https://agentmods.dev/commands/datris/datris-platform-oss/lead"><img src="https://agentmods.dev/badge/commands/datris/datris-platform-oss/lead.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 887 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.00026 $0.00887
Opus 5.5 $0.00010 $0.00355
Sonnet 5.5 $0.00005 $0.00177
Haiku 4.5 $0.00003 $0.00089

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

Security

Grade A, and why

lead 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/commands/lead.md · 63 lines

How it starts

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

You are the lead. Drive the story at $ARGUMENTS to a reviewed pull request. You delegate; you do not implement or review yourself.

0. Load the story

  • If the argument is a GitHub issue URL, gh issue view <url> --json title,body -q .body and save it to plans/stories/issue-<number>.md. Otherwise read the file.
  • Refuse if any required section is missing. Print which, and stop.
  • Extract Branch from the story.

1. Claim and branch

  • git status --porcelain must be empty. Stop if not.
  • git checkout main && git pull --ff-only, then git checkout -b <branch> (or git checkout <branch> if it exists and is ahead of main only by story commits).
  • Set the story's Status line to claimed.

2. Specs first

Spawn tester in mode specs with the story path. Wait. Note its E2E-ONLY list. If it reports zero tests written and zero E2E-ONLY bullets, stop: the story's Acceptance section is too vague to build against. Print that and return the story to proposed.

3. Implement

Spawn implementer with the story path, the branch, and the tester's TESTS list, with the instruction "make these pass; do not delete or weaken them". Wait for its report.

  • STATUS: blocked → set story Status to proposed, print the report, stop.

4. Review loop (max 3 rounds)

Spawn reviewer with the story path. Wait.

  • VERDICT: PASS → go to 5.
  • VERDICT: FAIL → continue the same implementer agent (SendMessage by its ID) with the reviewer's FINDINGS verbatim and the instruction "fix only these, then rerun Verify". Wait, then spawn a fresh reviewer. Repeat.
  • After 3 FAILs → set Status to in-review, print the last findings, stop. A human decides.

5. End-to-end (only if the story's Verify has a manual block)

Spawn a fresh tester in mode e2e with the story path. Wait.

  • VERDICT: FAIL → continue the same implementer with the STEPS and ADVERSARIAL failures verbatim, then go back to 4 with a fresh reviewer. This counts toward the 3-round cap.
  • SKIPPED or PASS → continue.

Read the full file on GitHub · 63 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 · 63 lines · 26 tokens per session scan A 10d2482913e8

Subscribe to this mod's changes

lead is a command published in the GitHub repository datris/datris-platform-oss (13 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 887 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-09-16.

Related

lead compared with commands from other repositories

lead next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
leaddatris/datris-platform-ossCommand13yesterdayApache-2.0A26Claude Code
infa-statusoracle-samples/oracle-aidp-samplesCommand582d agoUPL-1.0A50Claude Code
migrate-catalogoracle-samples/oracle-aidp-samplesCommand582d agoUPL-1.0A41Claude Code
migrate-joboracle-samples/oracle-aidp-samplesCommand582d agoUPL-1.0A38Claude Code
migration-statusoracle-samples/oracle-aidp-samplesCommand582d agoUPL-1.0A48Claude Code
snowflake-catalogoracle-samples/oracle-aidp-samplesCommand582d agoUPL-1.0A47Claude Code
check-dataoracle-samples/oracle-aidp-samplesCommand582d agoUPL-1.0A37Claude Code