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 skills/themattberman/openclaw-100k-posts-kit/the-forgenpx skills add TheMattBerman/openclaw-100k-posts-kit --skill the-forgegit clone --depth 1 https://github.com/TheMattBerman/openclaw-100k-posts-kitWrote 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/themattberman/openclaw-100k-posts-kit/the-forge)<a href="https://agentmods.dev/skills/themattberman/openclaw-100k-posts-kit/the-forge"><img src="https://agentmods.dev/badge/skills/themattberman/openclaw-100k-posts-kit/the-forge.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.00109 | $0.05938 |
| Opus 5 | $0.00055 | $0.02969 |
| Sonnet 5 | $0.00022 | $0.01188 |
| Haiku 4.5 | $0.00011 | $0.00594 |
Grade A, and why
the-forge 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 — 515 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Forge
Raw trend data goes in. Brand-native, source-traceable content concepts come out.
The Forge runs every input through three psychology frameworks in sequence, but it does NOT jump straight from trend to concept. It first identifies what made the source outlier work, decides which parts of that pattern are portable, translates those parts through the active brand voice, then outputs structured concepts you (or an agent) can take straight to a scheduler or content calendar.
When the upstream Pattern Report is provided as JSON, The Forge normalizes and prioritizes the richer Content DNA fields instead of only reading the markdown summary. That means it can reason from the source video's brick, why-it-worked explanation, and use-this-when guidance, not just the topic and angle.
When to use this skill:
- You have a trending topic, viral post, or emerging idea and need content angles
- You want to convert competitor content into original concepts
- You have raw research from
last30days,content-calendar, or similar skills - You need 3-5 distinct platform-specific concepts fast
What you get back: Numbered concepts, each with a hook, angle, body arc, format, platform fit, source attribution, and visible pattern lineage. When a structured Content DNA Pattern Report is available, The Forge also explicitly uses brick_name, brick_definition, why_it_worked, and plain_english_takeaway to improve transfer quality. Final concepts should surface that logic explicitly, including a source why-it-worked summary and a plain-English Use this when... line.
When iterating or debugging the skill: Read references/lessons.md for the practical learnings from real test runs, especially around hook simplicity, visible transfer, execution notes for experiments, and avoiding invented specifics.
The Three Frameworks
Framework 1: Puppet Strings (Why People Care)
Every piece of content pulls at least one of six core human drives. Match your content to the right drive and attention is almost automatic.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 515 lines · 109 tokens per session scan A 2346eb1c9a01
the-forge is a skill published in the GitHub repository TheMattBerman/openclaw-100k-posts-kit (20 stars, last pushed 5mo ago), licensed MIT. It adds 109 tokens to every session and 5,938 once invoked, about $0.0005 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…