ds-brief

ds-brief is a command for Claude Code from StamKavid/last-ds-mile. It costs 11 tokens per session (217 once invoked), scanned A, original, MIT.

A step for turning model-evaluation results into a one-page explanation written without technical terms.

In plain words
What is it for?
Use it to create a brief for audiences such as a board or a frontline team, after the evaluation report has been completed.
Why use it?
It prevents important findings from being buried in technical reports or misunderstood by readers unfamiliar with data science.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the last-ds-mile plugin — 29 skills, 17 commands, 3 agents, 4 hooks shipped together

Good fit Use it to create a brief for audiences such as a board or a frontline team, after the evaluation report has been completed.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/stamkavid/last-ds-mile/ds-brief
Install

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.

Clone the repo
git clone --depth 1 https://github.com/StamKavid/last-ds-mile

Made for: Claude Code.

Or install last-ds-mile, the plugin that ships this one along with the rest of its 29 skills, 17 commands, 3 agents, 4 hooks.

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 ds-brief

README.md
[![agentmods](https://agentmods.dev/badge/commands/stamkavid/last-ds-mile/ds-brief/github.svg)](https://agentmods.dev/commands/stamkavid/last-ds-mile/ds-brief)
Your own site
<a href="https://agentmods.dev/commands/stamkavid/last-ds-mile/ds-brief"><img src="https://agentmods.dev/badge/commands/stamkavid/last-ds-mile/ds-brief/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 ds-brief

Your own site · 80×15
<a href="https://agentmods.dev/commands/stamkavid/last-ds-mile/ds-brief"><img src="https://agentmods.dev/badge/commands/stamkavid/last-ds-mile/ds-brief.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 217 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.00011 $0.00217
Opus 5 $0.00005 $0.00109
Sonnet 5 $0.00002 $0.00043
Haiku 4.5 $0.00001 $0.00022

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

Security

Grade A, and why

ds-brief 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 9d 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.

commands/ds-brief.md · 17 lines

What it actually says

Invoke the ds-brief skill now via the Skill tool and follow its Core Process.

  1. Confirm .last-ds-mile/stages/09-report.md exists (the skill's gate check). If it doesn't, tell the user to run /ds-report first rather than drafting a brief from raw evaluation results.
  2. If $ARGUMENTS names an intended audience, tailor the framing (e.g. a board brief leans on the recommendation and the dollar figure; a frontline-team brief leans on "what happens next" and who owns the call) — the five required sections and the no-jargon rule apply regardless of audience.
  3. Write .last-ds-mile/stages/09b-brief.md per the skill's process.
  4. Show the brief to the user directly in the response, not only as a file write — this is the artifact most likely to be read immediately, not filed away.
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. 9d ago First seen · 17 lines · 11 tokens per session scan A 7907be230a4e

Subscribe to this mod's changes

ds-brief is a command published in the GitHub repository StamKavid/last-ds-mile (3 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 217 once invoked, about $0.0001 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-31.