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/content-start)<a href="https://agentmods.dev/commands/fatihkan/badi/content-start"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/content-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.00854 |
| Opus 5 | $0.00000 | $0.00427 |
| Sonnet 5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
content-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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content production session start command. Gives the daily content session a structured start, shows pending work, and sets priorities.
Required Tools
- Read (brand voice, calendar, existing content)
- Glob (workspace files)
- Grep (trend and pattern searches)
- Bash (date and file dates)
- Write (daily note)
Procedure (7 Steps)
Step 1: Load Context
Read these files:
.claude/workspace/marka-sesi.md— Brand tone and rules.claude/workspace/takvim/— The latest content calendar.claude/workspace/icerikler/— Last 10 content items.claude/workspace/senaryolar/— Last 5 video scriptsmemory.md— Active campaign or project
If these files do not exist, guide the user:
- No brand voice: suggest
badi content brand - No calendar: suggest
badi content calendar
Step 2: What's On Today?
List the content planned for today in the calendar:
- Which platforms get posts?
- Which themes are planned?
- Any pending drafts?
If nothing is planned for today, suggest a theme by day of week:
- Monday: Motivation / Week opener
- Tuesday: Educational / Tips
- Wednesday: Behind the scenes / Community
- Thursday: Product / Service
- Friday: Fun / Trends
- Saturday: UGC / Social proof
- Sunday: Inspiration / Weekly recap
Step 3: Pending Drafts
Scan the last 7 days of files in .claude/workspace/icerikler/ and .claude/workspace/senaryolar/. For each:
- File name and date
- Filled in, or still holding placeholders?
- For which platform?
Surface the unfinished (placeholder-containing) drafts.
Step 4: Recent Performance (if available)
If .claude/workspace/performans.md or a similar tracking file exists:
- Last week's 3 best-performing pieces
- The 3 lowest performers
- Trend note (rising/falling)
Step 5: Idea Suggestions
Generate ideas from these sources:
- This month's special days and events
- Current/trending topics (brand-fit ones)
- Evergreen content templates
- Pending FAQ or customer questions
Offer 3-5 concrete content ideas:
1. [Platform] — [Format] — [Topic]: [why it matters]
2. ...
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 · 139 lines · 0 tokens per session scan A b3174881460c
content-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 854 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.