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-status)<a href="https://agentmods.dev/commands/fatihkan/badi/content-status"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/content-status.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.00822 |
| Opus 5 | $0.00000 | $0.00411 |
| Sonnet 5 | $0.00000 | $0.00164 |
| Haiku 4.5 | $0.00000 | $0.00082 |
Grade A, and why
content-status 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content production status panel. Shows current output volume, pending items, calendar fit, and trend data.
Required Tools
- Read (workspace files)
- Glob (all content directories)
- Grep (placeholder and status detection)
- Bash (file dates, counting)
Procedure (5 Steps)
Step 1: Take Inventory
Scan all content files under .claude/workspace/:
icerikler/— Post and carousel countsenaryolar/— Video script countgorseller/— Visual brief counttakvim/— Calendar filesmarka-sesi.mdif present
Per file, extract metadata:
- Creation date
- Last modified date
- File size (fill indicator)
- Placeholder count
Step 2: Time-Based Grouping
Today: Created/edited today This week: Last 7 days This month: Last 30 days Old: 30+ days
For each group:
- Total count
- Completion ratio
Step 3: Completion Analysis
Determine each item's status:
COMPLETE (publish-ready):
- No placeholders
- All sections filled
- Visual note present
PARTIAL (needs editing):
- Some parts filled
- Main message set but details missing
DRAFT (freshly created):
- Mostly placeholders
- Basic structure present
STALE (archive candidate):
- Untouched for 30+ days
- Still holding placeholders
Step 4: Calendar Fit Check
If a calendar file exists:
- How many items planned?
- How many produced?
- How many published?
- Any delays?
Plan fit ratio: [percent]%
Step 5: Trends and Suggestions
Compute the last 2 weeks' trends:
- Production speed (average per day)
- Most produced format
- Least produced format (dormant channel warning)
- Stalls (zero-production days)
Generate suggestions:
- Neglected platforms
- Drafts starting to go stale
- Unfinished work
Output Format
=== BADI CONTENT STATUS ===
Date: [date] [time]
-------------------------------------------
INVENTORY
-------------------------------------------
Total Files: [count]
Posts/Carousels: [count]
Video Scripts: [count]
Visual Briefs: [count]
Calendars: [count]
Brand Voice: [PRESENT / MISSING]
-------------------------------------------
TIME DISTRIBUTION
-------------------------------------------
Today: [count] [====== ]
This Week: [count] [======== ]
This Month: [count] [==========]
Old: [count]
-------------------------------------------
COMPLETION
-------------------------------------------
Complete: [count] (%[ratio])
Partial: [count]
Draft: [count]
Stale: [count]
-------------------------------------------
CALENDAR FIT
-------------------------------------------
Planned: [count]
Produced: [count]
Published: [count]
Fit: [percent]%
-------------------------------------------
TREND (Last 2 Weeks)
-------------------------------------------
Daily Average: [count] items
Most Popular: [format] ([count])
Least: [format] ([count])
Stalls: [day count]
-------------------------------------------
WARNINGS
-------------------------------------------
- [staleness warning]
- [dormant channel]
- [overdue content]
-------------------------------------------
SUGGESTIONS
-------------------------------------------
1. [concrete suggestion]
2. [concrete suggestion]
3. [concrete suggestion]
-------------------------------------------
QUICK ACTIONS
-------------------------------------------
Finish a pending draft: [file]
Produce new content: badi content [type] "[topic]"
Create a calendar: badi content calendar "[period]"
Generate ideas: /content-idea
==========================
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 · 157 lines · 0 tokens per session scan A d7923175a6ef
content-status 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 822 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
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
qa
Systematic QA testing of a web application — diff-aware, tiered, with fix-and-verify loop.
review-pr
Perform a comprehensive code review of a pull request.
security-audit
Comprehensive security audit with scored posture assessment.