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/indranilbanerjee/contentforgeWrote 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/indranilbanerjee/contentforge/audit-content)<a href="https://agentmods.dev/commands/indranilbanerjee/contentforge/audit-content"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/contentforge/audit-content/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/indranilbanerjee/contentforge/audit-content"><img src="https://agentmods.dev/badge/commands/indranilbanerjee/contentforge/audit-content.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.00513 |
| Opus 5.5 | $0.00007 | $0.00205 |
| Sonnet 5.5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
audit-content 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 21d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- audit-content — 100% identical, 3 lines differ
- audit-content — 95% identical, 0 lines differ
What it actually says
Audit Content
This command is a thin wrapper. The complete audit procedure — including the canonical
freshness scoring model — lives in skills/cf-audit/SKILL.md.
Read that file and execute it end to end. Do not improvise a different scoring model here.
Trigger
User runs /contentforge:audit-content or asks to audit their content, check for content
decay, find content gaps, or assess content health.
Gather inputs
If not provided in the arguments, ask before proceeding:
- Content source — Google Drive folder URL, WordPress site URL, CSV file
(columns:
title,url,publish_date,content_type,word_count), or a pasted list - Audit scope —
freshness|gaps|both(default) - Optional — aging threshold in months (default 12), brand filter, target keywords CSV, competitor URLs
Canonical scoring (defined in the skill — summarized here for orientation only)
Freshness = 4 factors: Age 35% / Statistics currency 25% / Link health 20% / Citation recency 20%. Bands: Fresh 90-100, Good 70-89, Aging 50-69, Stale 30-49, Expired 0-29. The skill file is authoritative if this summary ever disagrees.
Execute
Follow skills/cf-audit/SKILL.md in full:
load inventory → freshness scoring → coverage gap analysis → performance analysis
(if analytics connected) → prioritized recommendations (refresh / new / retire).
After the audit
Ask: "Would you like me to:
- Create content briefs for the top gap opportunities? (
/contentforge:content-brief) - Start refreshing the highest-priority piece? (
/contentforge:content-refresh) - Build a quarterly content calendar from these recommendations? (
/contentforge:cf-calendar) - Re-research the SERP and competitors for a specific topic in depth? (
/contentforge:cf-brief) - Export this audit to a spreadsheet?"
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.
- 21d ago Changed · +1 lines · +3 tokens per session 8b3a138fffcd
- 2mo ago First seen · 46 lines · 14 tokens per session scan A 8b4961806a58
audit-content is a command published in the GitHub repository indranilbanerjee/contentforge (32 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 513 once invoked, about $0.0001 per session on Opus 5.5. 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-30.
Other commands, from other repositories
engagement
Drive the 12-Part engagement by subcommand: start, next, status, validate, loop. "advance to the next part".
status
Show production status for the active brand and month. "where are we on this month".
finalize
Finalize the month and package approved content for delivery. "close out the month".
verify-outcome
Recompute a recorded outcome from raw data and compare it against what was claimed.
content-brief
Generate a content brief for a keyword or topic: intent, competitors, outline. "brief this keyword".
edit-post
Edit an existing post's copy, visual direction or metadata. "tweak the copy on P07".