dbt_duckdb_demo_public: Command for Claude Code

.claude/commands/team.md

team is a command for Claude Code from edwinweber/dbt_duckdb_demo_public. It costs 0 tokens per session (412 once invoked), scanned A, original, MIT.

A command that brings together the relevant specialist agents in a project’s .claude/agents/ folder and combines their responses into one answer.

In plain words
What is it for?
Use it for debugging, feature work, architecture decisions, broad technical questions, or documentation tasks that benefit from several project agents.
Why use it?
It avoids relying on a single viewpoint when a task needs investigation, design, implementation, or writing expertise.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths.

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

Reuse

Borrowing it

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

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 team

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/edwinweber/dbt_duckdb_demo_public/team"><img src="https://agentmods.dev/badge/commands/edwinweber/dbt_duckdb_demo_public/team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 412 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.00000 $0.00412
Opus 5 $0.00000 $0.00206
Sonnet 5 $0.00000 $0.00082
Haiku 4.5 $0.00000 $0.00041

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

Security

Grade A, and why

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 10d 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/team.md · 38 lines

What it actually says

Analyse the following task, identify ALL agents from the project team in .claude/agents/ whose expertise is relevant, spawn them, and synthesise their outputs into a single cohesive answer for the user.

Agent roles

  • investigator — diagnose broken or unexpected behaviour; read-only, evidence-based
  • architect — design decisions, trade-offs, hard-to-reverse choices
  • engineer — implementation: Python, dbt, Dagster, dlt, DuckDB schema, tests
  • writer — documentation, blog posts, explanations

How to decide which agents to invoke

Invoke every agent whose lens adds something the others would miss. A task rarely needs only one.

Task type Agents
Pure debug / something is broken investigator only
New feature, no design ambiguity engineer + writer (if docs needed)
New feature with architectural implications architectengineerwriter
Design question only architect only
Documentation only writer only
Broad question (e.g. "how should we approach X") architect + engineer (parallel perspectives)

When in doubt, spawn more rather than fewer — the user asked for the full team.

Execution order

  • Parallel: agents with no dependency on each other run simultaneously.
  • Sequential: architect before engineer (design before code); engineer before writer (implementation before docs); investigator before anyone else when the root cause is unknown.
  • Pass relevant output from earlier agents as context when spawning later ones.

Output

Synthesise all agent responses into one structured answer. Label each section by the agent that produced it so the user knows which lens each part comes from. Do not just concatenate — integrate where the agents agree, and surface disagreements explicitly.

Task

$ARGUMENTS

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. 10d ago First seen · 38 lines · 0 tokens per session scan A aff20eaea3ea

Subscribe to this mod's changes

team is a command published in the GitHub repository edwinweber/dbt_duckdb_demo_public (49 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 412 tokens. 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.