start

start is a command for Claude Code from fatihkan/badi. It costs 0 tokens per session (715 once invoked), scanned A, original, MIT.

A session-start command for either introducing a new project or preparing for the day's work. It scans the project files, identifies technologies and tools, asks about goals and constraints, and records the context.

In plain words
What is it for?
Use it for new-project onboarding and daily kickoffs, including finding languages, frameworks, databases, deployment tools, tests, and project preferences.
Why use it?
It avoids beginning work without understanding the codebase, its technology choices, the user's priorities, or the project's working rules.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Part of the badi plugin — 81 skills, 86 commands, 30 agents, 7 hooks shipped together

Good fit Use it for new-project onboarding and daily kickoffs, including finding languages, frameworks, databases, deployment tools, tests, and project preferences.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/fatihkan/badi/start
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/fatihkan/badi

Made for: Claude Code.

Or install badi, the plugin that ships this one along with the rest of its 81 skills, 86 commands, 30 agents, 7 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 start

README.md
[![agentmods](https://agentmods.dev/badge/commands/fatihkan/badi/start.svg)](https://agentmods.dev/commands/fatihkan/badi/start)
Your own site
<a href="https://agentmods.dev/commands/fatihkan/badi/start"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/start.svg" alt="Measured on agentmods" 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 715 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.00715
Opus 5 $0.00000 $0.00358
Sonnet 5 $0.00000 $0.00143
Haiku 4.5 $0.00000 $0.00072

Measured today against content hash ee7a864c2b12, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

start 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 today.

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/start.md · 112 lines

How it starts

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

Badi session start command. Runs new-project onboarding or a daily kickoff.

Required Tools

  • Bash (filesystem access)
  • Read (memory and context files)
  • Glob (project structure scan)
  • Grep (code search)
  • Write (daily note creation)

Mode Selection

Ask the user: "New-project onboarding or a daily kickoff?"


A) New-Project Onboarding

Step 1: Project Structure Scan

  • Scan all files and folders in the root directory
  • Find manifest files like package.json, Cargo.toml, pyproject.toml, go.mod
  • Detect infrastructure files like .env.example, docker-compose.yml, Makefile

Step 2: Tech Stack Detection

  • Programming languages and versions
  • Frameworks and libraries
  • Databases and external services
  • CI/CD and deploy infrastructure
  • Test tooling

Step 3: Context Questions (4 Questions)

Ask the user:

  1. "What is the core purpose of this project and who is its target user?"
  2. "What is your most important priority right now?"
  3. "Any technical constraints or decisions I should know about?"
  4. "What are your working-style preferences? (commit style, branch strategy, test expectations)"

Step 4: Memory Creation

Create or update memory.md with what was gathered:

  • Project summary
  • Tech stack
  • User preferences
  • Important file paths
  • Architecture notes

Step 5: Skill Suggestions

Suggest the Badi commands that fit the project:

  • Which commands will be most useful for this project
  • A suggested daily workflow
  • Note any custom command needs

B) Daily Kickoff

Step 1: Get the Date

  • Determine today's date in DDMMYY format (example: 090426)

Step 2: Load Context

  • Read memory.md
  • Read knowledge-base.md if it exists
  • Check the latest session notes

Step 3: Create the Daily Note

Create daily-notes/DDMMYY.md:

# Daily Note - [DD.MM.YYYY]

## Focus Areas
- [ ] ...

## Notes
...

## Decisions
...

## Tomorrow's Work
...

Step 4: Review the Task Board

  • List the open tasks
  • Check work left from the previous session
  • Detect completed-but-not-closed tasks

Read the full file on GitHub · 112 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. today First seen · 112 lines · 0 tokens per session scan A ee7a864c2b12

Subscribe to this mod's changes

start is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 715 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-09-06.