content-perf

content-perf is a command for Claude Code from fatihkan/badi. It costs 0 tokens per session (465 once invoked), scanned A, original, MIT.

A command for recording and reviewing the performance of published content across social platforms. It tracks engagement, audience reach, production time, trends, and engagement relative to effort.

In plain words
What is it for?
Use it to add post metrics, view weekly or monthly summaries, compare trends, filter by platform, and see which platform produces the most engagement for the time spent.
Why use it?
It keeps results in one place so you can compare periods and platforms instead of judging content from memory.

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-perf
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.

Wrote 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.

agentmods badge for content-perf

README.md
[![agentmods](https://agentmods.dev/badge/commands/fatihkan/badi/content-perf.svg)](https://agentmods.dev/commands/fatihkan/badi/content-perf)
Your own site
<a href="https://agentmods.dev/commands/fatihkan/badi/content-perf"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/content-perf.svg" alt="Measured on agentmods" height="20"></a>
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 465 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.00465
Opus 5 $0.00000 $0.00233
Sonnet 5 $0.00000 $0.00093
Haiku 4.5 $0.00000 $0.00047

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

Security

Grade A, and why

content-perf 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.

.claude/commands/content-perf.md · 82 lines

What it actually says

Content performance tracking command. Tracks likes, comments, reach, and ROI for published content.

Required Tools

  • Bash (badi content perf)

Procedure

Step 1: Add Data

Record the metrics after every publish:

badi content perf add --file 2026-04-19-topic.md \
  --platform instagram \
  --likes 150 --comments 12 --shares 5 --saves 20 \
  --reach 2500 \
  --effort 1.5

Parameters:

  • --file — Content file name
  • --platform — instagram/twitter/linkedin/tiktok/facebook
  • --likes/--comments/--shares/--saves/--reach — Metrics
  • --effort — Production time (hours)

Step 2: Reports

badi content perf              # Weekly summary (default)
badi content perf --week
badi content perf --month
badi content perf list         # All records

Step 3: Trend Analysis

badi content perf --trend

Previous vs. current period comparison:

  • Total engagement change (%)
  • Platform-level trends

Step 4: ROI Analysis

badi content perf --roi

Engagement/effort ratio per platform. Which platform pays the most for your hour?

Step 5: Platform Filter

badi content perf --platform instagram --month

Step 6: Interpretation + Action

Based on the report, tell the user:

  • Best performer: "Shall we repeat this format?"
  • Low ROI: "Rethink the time investment on this platform?"
  • Negative trend: "Should the content mix be revised?"

Step 7: Weekly Routine

Thursday/Friday evening weekly evaluation:

badi content perf --trend      # Evaluate the week
badi content plan              # Plan next week

Example

/content-perf                  # Weekly summary
/content-perf --trend          # Trend comparison
/content-perf --roi            # ROI ranking
/content-perf add --file ... --platform linkedin --likes 85 ...
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. 4d ago First seen · 82 lines · 0 tokens per session scan A cf07d6f2e5fe

Subscribe to this mod's changes

content-perf 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 465 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.