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/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/commands/dokkabei97/forged-claude-code/social-post-gen)<a href="https://agentmods.dev/commands/dokkabei97/forged-claude-code/social-post-gen"><img src="https://agentmods.dev/badge/commands/dokkabei97/forged-claude-code/social-post-gen.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.1 | $0.00029 | $0.01011 |
| Opus 5 | $0.00015 | $0.00505 |
| Sonnet 5 | $0.00006 | $0.00202 |
| Haiku 4.5 | $0.00003 | $0.00101 |
Grade A, and why
social-post-gen 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 7d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/social-post-gen - Social Media Post Generator
Triggers
- When announcing features, launches, or milestones
- When creating regular social media content
- When adapting content for different platforms
Usage
/social-post-gen [topic or announcement]
/social-post-gen "We just launched v2.0 with AI features"
/social-post-gen --platform twitter [topic]
/social-post-gen --platform linkedin [topic]
/social-post-gen --platform all [topic]
/social-post-gen --type launch|tip|milestone|engagement
Behavioral Flow
Phase 1: Context Analysis
1. Identify post type (launch / tip / milestone / engagement / thought leadership)
2. Determine target audience
3. Reference brand voice guidelines (if available)
4. Identify key message and CTA
Phase 2: Platform-Specific Generation
Twitter/X:
Format: Single tweet or thread
Length: < 280 chars per tweet
Style: Conversational, punchy, witty
Elements: Hook in first line, line breaks, optional emoji
Hashtags: 1-2 max, at end
Media: Suggest screenshot/GIF
Template:
[Hook — bold claim or question]
[Supporting point]
[Social proof or data point]
[CTA]
#hashtag1 #hashtag2
LinkedIn:
Format: Long-form post
Length: 1,300 chars optimal
Style: Professional but personal, storytelling
Elements: Strong first 2 lines (before fold), line breaks between paragraphs
Hashtags: 3-5 at end
Template:
[First line — hook that stops scrolling]
[Second line — continuation or surprise]
[Story or insight — 3-5 short paragraphs]
[Lesson or takeaway]
[Question to drive comments]
#hashtag1 #hashtag2 #hashtag3
Instagram (Caption):
Format: Caption with suggested visual description
Length: First 125 chars most important (preview)
Style: Authentic, visual-first
Elements: Emoji-friendly, call to save/share
Hashtags: 20-30 in first comment (not caption)
Template:
[Hook — first line that appears in feed]
[Story or value — 3-4 short paragraphs]
[CTA — "Save this for later" / "Tag someone who needs this"]
.
.
.
[Hashtags in separate block or first comment]
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.
- 7d ago First seen · 169 lines · 29 tokens per session scan A a42bedd4e7e3
social-post-gen is a command published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 1,011 once invoked, about $0.0001 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 commands, from other repositories
tour
Tour this project's memory — what's captured, where it lives, how to recall it (core-memory-kit).
p3-ux-wireframes
Creates wireframes (ASCII art) for the most important screens with interaction descriptions.
dare-dag-viz
Gera diagrama interativo .excalidraw a partir do dare-dag.yaml atual, com cores semânticas por complexidade e status visual das tasks.
dare-llm-integration
Integração segura e eficiente com LLMs (Gemini, Claude, OpenAI, Ollama) em projetos DARE.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
forge-insights
Analyze past sessions for error patterns, file activity, and recommendations.