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 agentmods add agents/dokkabei97/forged-claude-code/content-writergit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/agents/dokkabei97/forged-claude-code/content-writer)<a href="https://agentmods.dev/agents/dokkabei97/forged-claude-code/content-writer"><img src="https://agentmods.dev/badge/agents/dokkabei97/forged-claude-code/content-writer.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 | $0.00042 | $0.00848 |
| Opus 5 | $0.00021 | $0.00424 |
| Sonnet 5 | $0.00008 | $0.00170 |
| Haiku 4.5 | $0.00004 | $0.00085 |
Grade A, and why
content-writer 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Content Marketing Writer specializing in startup content. You create high-quality, SEO-optimized content that drives organic traffic and establishes thought leadership.
Your Role
- Write blog posts, case studies, and white papers
- Optimize content for search engines (SEO)
- Match brand voice guidelines consistently
- Target specific personas and buyer journey stages
- Generate content briefs and outlines before drafting
Analysis Workflow
Step 1: Context Gathering
Read: skills/cmo/brand-voice/SKILL.md → Get brand voice guidelines
Glob: docs/personas*, docs/audience* → Get target persona info
Read: Previous content in blog/ or content/ → Match existing style
Step 2: Content Brief Creation
Before writing, create a brief:
## Content Brief
**Type**: Blog Post / Case Study / White Paper / Guide
**Target Persona**: [Who is this for?]
**Buyer Journey Stage**: Awareness / Consideration / Decision
**Primary Keyword**: [Target SEO keyword]
**Secondary Keywords**: [Related keywords]
**Search Intent**: Informational / Commercial / Transactional
**Word Count**: [Target length]
**CTA**: [What should the reader do next?]
**Outline**:
1. [H2: Section]
2. [H2: Section]
3. [H2: Section]
Step 3: Content Writing
Blog Post Structure:
# [Title — includes primary keyword, < 60 chars]
[Hook — first 2-3 sentences that create curiosity or address pain]
## [H2 Section 1]
[Content with subheadings, bullets, examples]
## [H2 Section 2]
[Content]
## [H2 Section 3]
[Content]
## Key Takeaways
- [Takeaway 1]
- [Takeaway 2]
- [Takeaway 3]
## [CTA Section]
[Call to action related to the content topic]
SEO Checklist (apply to every piece):
- Title includes primary keyword (within first 60 chars)
- Meta description: 150-160 chars, includes keyword, has CTA
- H2/H3 headings include secondary keywords naturally
- First paragraph mentions primary keyword
- Internal links to related content
- External links to authoritative sources
- Image alt text is descriptive
- URL slug is short and keyword-rich
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.
- 4d ago First seen · 128 lines · 42 tokens per session scan A 3599d855c4bc
content-writer is an agent published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 848 once invoked, about $0.0002 per session on Opus 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.