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 skills add indranilbanerjee/contentforge --skill cf-templategit 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/skills/indranilbanerjee/contentforge/cf-template)<a href="https://agentmods.dev/skills/indranilbanerjee/contentforge/cf-template"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/contentforge/cf-template/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/skills/indranilbanerjee/contentforge/cf-template"><img src="https://agentmods.dev/badge/skills/indranilbanerjee/contentforge/cf-template.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 3 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 469 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00028 | $0.04443 |
| Opus 5.5 | $0.00011 | $0.01777 |
| Sonnet 5.5 | $0.00006 | $0.00889 |
| Haiku 4.5 | $0.00003 | $0.00444 |
Grade A, and why
cf-template 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 18d 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:
- cf-template — 100% identical, 2 lines differ
- cf-template — 91% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 493 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Custom Content Template Manager
Create and manage custom content type templates beyond the 8 built-in types (article, blog, whitepaper, faq, research-paper, video-script, case-study, newsletter). Define section structure, word count ranges, readability targets, citation requirements, and quality standards — then use the template with /contentforge:create-content for consistent, repeatable content production.
Where templates live
- Built-in templates (read-only):
templates/content-types/inside the installed plugin — article, blog, whitepaper, faq, research-paper, video-script, case-study, newsletter. - Custom templates (user-created):
~/.claude-marketing/_templates/— never write into the installed plugin directory. Plugin updates and reinstalls wipe the plugin folder; anything saved there is lost.~/.claude-marketing/_templates/survives updates.
When to Use
Use /contentforge:cf-template when:
- You need a content type not covered by the 8 built-in templates (product comparison, landing page copy, press release, webinar outline, etc.)
- You want to standardize a content format your team produces regularly
- You need to modify an existing template (e.g., add a section to the article template)
- You're onboarding a client who has specific content format requirements
- You want to import a content structure from an example file
For producing content using a template, use /contentforge:create-content --type=custom:template-name.
For the 8 built-in templates, see templates/content-types/ (these ship with the plugin and cannot be deleted).
What This Command Does
- Define Template — Specify content type name, base type (or custom), word count range, readability target, and citation requirements
- Create Section Structure — Define sections with names, descriptions, word count allocations, and ordering
- Set Quality Standards — Readability target (grade level), citation density, keyword placement rules, and custom quality criteria
- Generate Template File — Create the template .md file in
~/.claude-marketing/_templates/ - Validate Pipeline Compatibility — Test that the template works with all ContentForge pipeline phases
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.
- 18d ago Changed · -132 tokens per session 2f828fb87491
- 1mo ago First seen · 493 lines · 160 tokens per session scan A 2e02e15d3dd5
cf-template is a skill published in the GitHub repository indranilbanerjee/contentforge (32 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 4,443 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 skills, from other repositories
four-core-documents
Produce the Part 3 Four Core Documents: business, segmentation, positioning, DMFlow. "produce the four core documents".
continuous-improvement-loop
Run the Part 12 continuous improvement loop into a quarterly brief for leadership. "produce the quarterly improvement brief".
seo-plan
Build a 12-month SEO plan that scores four pillars and phases the roadmap. "build an SEO strategy".
aeo-audit
Run a one-time AEO audit of six AI answer engines, scored per surface. "check our AI search visibility".
c2pa-metadata
Embed C2PA provenance in AI-generated images, video or PDF by script. "add content credentials to this asset".
growth-plan
Produce the Part 8 Growth Plan: one strategy with scenario forecasts and a 30/60/90. "write the strategy document for the client".