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.
npx agentmods add commands/fatihkan/badi/content-ideagit 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-idea)<a href="https://agentmods.dev/commands/fatihkan/badi/content-idea"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/content-idea.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 | $0.00000 | $0.00741 |
| Opus 5 | $0.00000 | $0.00370 |
| Sonnet 5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
content-idea 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content idea generation command. Creates a structured idea list for a topic, theme, or platform.
Required Tools
- Read (brand voice, past content, trend notes)
- Grep (repeat check)
- Glob (archive scan)
- Bash (trend data, time)
Procedure (5 Steps)
Step 1: Idea Parameters
From the user:
- Topic area: General theme or sector (optional)
- Platform: For which platform? (if any)
- Format: Post / Carousel / Video / All
- Tone: Must match the brand voice (automatic)
- Count: How many ideas? (default: 10)
- Goal: Engagement / Sales / Awareness / Education
Step 2: Source Scan
Feed from idea sources:
Internal sources:
- Content produced in the last 30 days (repeat prevention)
- Pending drafts (improvable)
- Customer questions / FAQ
- Current product / service list
External sources (if available):
- Seasonal calendar (month / week)
- Special days (world X day, holidays)
- Industry trends
- Popular format examples
Step 3: Generate 10 Ideas
Categorize by different angles:
Educational (3-4 ideas):
- How-to
- X-tip lists
- Common mistakes
- Beginner guides
Story (2-3 ideas):
- Personal experience
- Customer success story
- Behind the scenes
Fun/Trend (2-3 ideas):
- Meme adaptation
- Trending format
- Challenge
Sales-Focused (1-2 ideas):
- Product promo
- Discount announcement
- Case study
Step 4: Quick Brief per Idea
A mini summary for each idea:
[number]. [Platform] — [Format] — [Title]
Tone: [tone]
Hook: [first-sentence idea]
Message: [one-sentence summary]
CTA: [suggested call]
Impact: [LOW / MEDIUM / HIGH]
Effort: [LOW / MEDIUM / HIGH]
Step 5: Priority Suggestion
Rank by impact/effort ratio:
- Quick Win (High impact, low effort) — Do today
- Strategic (High impact, high effort) — Plan it
- Filler (Low impact, low effort) — When the chance comes
- Avoid (Low impact, high effort) — Drop from the list
Output Format
=== BADI CONTENT IDEAS ===
Date: [date]
Topic Area: [area]
Platform: [platform]
Count: [number]
-------------------------------------------
QUICK WINS (Do Today)
-------------------------------------------
1. [Platform] [Format]: [title]
Hook: [sentence]
Message: [summary]
CTA: [call]
Time: ~[minutes]
2. ...
-------------------------------------------
STRATEGIC (Plan)
-------------------------------------------
3. [Platform] [Format]: [title]
...
-------------------------------------------
FILLER
-------------------------------------------
4. ...
-------------------------------------------
SPECIAL DAY TIE-INS
-------------------------------------------
Upcoming special days:
- [date]: [event] -> idea: [suggestion]
-------------------------------------------
NEXT STEP
-------------------------------------------
Quick start:
badi content post "[chosen idea]"
badi content carousel "[chosen idea]"
/content-generate
=============================
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.
- 4d ago First seen · 129 lines · 0 tokens per session scan A 45ee6c5551ef
content-idea is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 741 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-31.
Other commands, from other repositories
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
sonarqube
Analyze SonarCloud quality issues for a specific PR.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
scaffold
Interactive coach that asks 4-5 questions to determine whether you need an agent, command, skill, hook, or rule — then generates a ready-to-use template. Usage: /scaffold (no arguments — starts the coaching session).
investigate
Systematic root-cause debugging — find the cause before writing any fix.