post-forge-feature

A writing assistant for creating a short Twitter/X post about a ForgeCode feature, alongside a demonstration video. It first uses source code, documentation, or changelogs to understand the feature.

In plain words
What is it for?
Use it to draft a two- or three-sentence ForgeCode feature post with an approved tone, wording, and hashtag line, then review it before finalizing.
Why use it?
It helps turn a technical feature into a concise developer-focused post without making unsupported claims or explaining everything the video already shows.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/tailcallhq/forgecode/post-forge-feature
Any agent
npx skills add tailcallhq/forgecode --skill post-forge-feature
Clone the repo
git clone --depth 1 https://github.com/tailcallhq/forgecode

Made for: Claude Code, Codex.

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 338 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00051 $0.00338
Opus 5 $0.00026 $0.00169
Sonnet 5 $0.00010 $0.00068
Haiku 4.5 $0.00005 $0.00034

Measured 2d ago against content hash 94b54017d7a7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

post-forge-feature 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.forge/skills/post-forge-feature/SKILL.md · 34 lines

What it actually says

Post ForgeCode Feature

Generate a punchy, developer-friendly Twitter/X post for a ForgeCode feature. The post always accompanies a video, so no need to describe every detail; the video does the showing.

Workflow

  1. Understand the feature: use tools to read the relevant source code, docs, or changelogs. Answer:

    • What does it do?
    • When would a developer reach for it?
    • What pain does it remove?
  2. Craft the post: follow the constraints in references/style-guide.md.

  3. Present for approval: show the post and ask if the user wants tweaks before finalizing.

Key Constraints

  • 2-3 sentences max (fits ~280 chars).
  • No filler phrases ("excited to announce", "game changer", "introducing").
  • Always refer to the product as "ForgeCode", never "Forge" alone.
  • No em dashes anywhere in the post.
  • Lead with the developer benefit or the problem solved, not the feature name.
  • The video is attached. Do not say "watch the video" or describe what is in it.
  • End with a relevant hashtag line (see style guide for approved tags).

Reference Files

  • references/style-guide.md: tone, vocabulary, approved hashtags, and example posts. Read this before drafting.
Files

What ships with it

1 file 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.

Changes

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.

  1. 2d ago First seen · 34 lines · 51 tokens per session scan A 94b54017d7a7

Subscribe to this mod's changes

post-forge-feature is a skill published in the GitHub repository tailcallhq/forgecode (7,599 stars, last pushed 2d ago), licensed Apache-2.0. It adds 51 tokens to every session and 338 once invoked, about $0.0003 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.