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 justrach/codegraff2 --skill post-forge-featuregit clone --depth 1 https://github.com/justrach/codegraff2Wrote 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/justrach/codegraff2/post-forge-feature)<a href="https://agentmods.dev/skills/justrach/codegraff2/post-forge-feature"><img src="https://agentmods.dev/badge/skills/justrach/codegraff2/post-forge-feature/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/justrach/codegraff2/post-forge-feature"><img src="https://agentmods.dev/badge/skills/justrach/codegraff2/post-forge-feature.svg" alt="Reviewed on agentmods" width="80" 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.00051 | $0.00338 |
| Opus 5.5 | $0.00020 | $0.00135 |
| Sonnet 5.5 | $0.00010 | $0.00068 |
| Haiku 4.5 | $0.00005 | $0.00034 |
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 2mo 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.
This is a copy
100% identical to post-forge-feature — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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
-
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?
-
Craft the post: follow the constraints in
references/style-guide.md. -
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.
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.
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.
- 2mo ago First seen · 34 lines · 51 tokens per session scan A 94b54017d7a7
post-forge-feature is a skill published in the GitHub repository justrach/codegraff2 (27 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 51 tokens to every session and 338 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to post-forge-feature, differing in 0 lines, and is treated as a copy.
post-forge-feature compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| post-forge-featurejustrach/codegraff2 | Skill | 27 | 4mo ago | Apache-2.0 | A | 51 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | today | MIT | A | 103 | Claude Code |