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.
git clone --depth 1 https://github.com/fatihkan/badiWrote 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.
[](https://agentmods.dev/commands/fatihkan/badi/start)<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>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.
| Model | Per session | Once 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 |
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.
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:
- "What is the core purpose of this project and who is its target user?"
- "What is your most important priority right now?"
- "Any technical constraints or decisions I should know about?"
- "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
DDMMYYformat (example: 090426)
Step 2: Load Context
- Read
memory.md - Read
knowledge-base.mdif 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
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.
- today First seen · 112 lines · 0 tokens per session scan A ee7a864c2b12
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.
Other commands, from other repositories
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
plan-ceo-review
Strategic product gate — challenge the brief, find the 10-star product hiding inside the request, before writing any code.
routines-discover
Analyzes the current project to surface high-value Routines use cases across the three trigger types (schedule, API, GitHub events). Usage: /routines-discover.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
review-pr
Perform a comprehensive code review of a pull request.
git-worktree-clean
Clean up stale git worktrees with merged branch detection and disk usage report.