content-close

A command for closing a daily content session. It reviews the day's files, checks drafts for unfinished placeholders, suggests publishing plans, and prepares notes for the next day.

In plain words
What is it for?
Use it to review posts, videos, visual briefs, and calendar updates in the workspace, then record completion status and tomorrow's preparation notes.
Why use it?
It brings scattered content work into one end-of-day review and reveals drafts that are incomplete before they are published.

Command for Claude Code

Part of the badi plugin — 28 commands, 30 agents shipped together

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.

agentmods
npx agentmods add commands/fatihkan/badi/content-close
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 28 commands, 30 agents.

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 813 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00813
Opus 5 $0.00000 $0.00407
Sonnet 5 $0.00000 $0.00163
Haiku 4.5 $0.00000 $0.00081

Measured 3d ago against content hash 19d3a1fd9453, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

content-close 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 3d 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.

.claude/commands/content-close.md · 144 lines

How it starts

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

Content session close command. Summarizes the day's output, prepares for tomorrow, and notes learnings.

Required Tools

  • Read (today's content, notes)
  • Glob (files created today)
  • Grep (placeholder check)
  • Write (daily note update)
  • Bash (date and file listing)

Procedure (6 Steps)

Step 1: Collect Today's Output

Find today's files under .claude/workspace/:

  • icerikler/ — Posts and carousels
  • senaryolar/ — Videos
  • gorseller/ — Visual briefs
  • takvim/ — Calendar updates

For each file:

  • File name
  • Content type
  • Complete? (any placeholders?)
  • For which platform?

Step 2: Completion Check

Look for placeholder markers in every draft:

  • [...] (bracketed placeholders)
  • TODO, TBD, FIXME
  • Empty sections

Complete: No placeholders, publish-ready Partial: Some parts filled, some missing Draft: Mostly empty

Step 3: Publishing Plan

Suggest publish times for completed content:

  • Platform-optimal hours
  • Theme fit (day/time)
  • Suggestion to add to the calendar
[Content] -> [Platform] -> [Day] [Time]

Step 4: Prepare for Tomorrow

Create a prep note for tomorrow:

  • What's on tomorrow? Check the calendar
  • Any unfinished drafts? Make them tomorrow's first job
  • Any ongoing series? (carousel series, video series)
  • Any trend opportunities? (current events, special days)

Step 5: Learnings and Notes

Note today's insights:

  • What went well? (content that came easily)
  • What was hard? (where you got stuck)
  • Any new ideas born? (for future use)
  • Does the brand voice need a correction?

Learnings can be nominated into knowledge-nominations.md.

Step 6: Close the Session Note

Update .claude/workspace/icerik-notlari/[date].md:

# Content Notes — [date]

## Today's Priority
[the priority set in the morning]

## Completed
- [x] [content 1] — [platform]
- [x] [content 2] — [platform]

## Partially Completed
- [ ] [content 3] — [what's missing]

## Ideas / Notes
- [new idea]
- [learning]

## For Tomorrow
- [ ] [priority 1]
- [ ] [priority 2]

## Performance Notes
[numbers if any]

Read the full file on GitHub · 144 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. 3d ago First seen · 144 lines · 0 tokens per session scan A 19d3a1fd9453

Subscribe to this mod's changes

content-close 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 813 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.