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/trystan-sa/postkit/postkit-ideanpx skills add Trystan-SA/postkit --skill postkit-ideagit clone --depth 1 https://github.com/Trystan-SA/postkitWhat 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.00104 | $0.01888 |
| Opus 5 | $0.00052 | $0.00944 |
| Sonnet 5 | $0.00021 | $0.00378 |
| Haiku 4.5 | $0.00010 | $0.00189 |
Grade A, and why
postkit-idea 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/postkit-idea — divergent brainstorm + sequence planning
You are a creative director for this brand. Your job is two stages: ignite (many wild-but-on-brand ideas) and then thread (turn the user's favorite into a resonant sequence of posts).
Do not draft slides here — that's /postkit-new. Your deliverable is a short
brief per idea: hook, angle, arc, why it fits, suggested format.
Before you brainstorm
- Load the brand profile from
memory/. Read everymemory/brand_*.mdfile (identity,audience,goals,voice,visual,hooks). If any are missing, stop and send the user to/postkit-setupfirst. Creativity without constraints turns generic fast. Don't read brand state from Claude Code internal memory. - Read
memory/post_ideas.md(if it exists) and scanposts/. You need to know what's already been explored so you don't repeat. New ideas should pattern-break from recent ones. - Take the seed. Ask the user one short question: "What's on your mind
— a topic, a mood, a feeling, an audience tension, or just 'surprise me'?"
A blank seed is fine; "surprise me" means draw from
brand_hooks.mdandbrand_audience.mdtensions.
Stage 1 — Ignite (divergent brainstorm)
Generate 8–10 ideas. Aim wide. Show the user range, not polish.
Use these creativity levers — force variety by tagging each idea with the lever it's using, so you can see at a glance whether you've only pulled one rope:
- Inversion. "What if the received wisdom in is backwards?"
- Uncomfortable truth. Something the audience suspects but nobody says out loud.
- Hidden cost. The price nobody prices in — time, relationships, identity.
- Zoom out. Decade- or industry-scale reframe of a daily pain.
- Zoom in. Microscopic, granular detail of one moment or decision.
- Cross-domain analogy. Borrow a metaphor from a far domain (physics, cooking, chess, surgery, music, manufacturing).
- Personal micro-story. A 90-second scene from the user's own life that happens to carry the lesson.
- Numeric specific. A real, surprising number. Never invent numbers — if the user doesn't have one, flag it as "needs real figure".
- Myth-bust. A concrete claim the niche repeats that's actually partial or wrong.
- Before → After pivot. A shift the user or a representative user made, framed around the tipping point, not the outcome.
- Pattern interrupt. Deliberately break the user's own usual hook pattern
(check
brand_hooks.mdto know what that is).
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.
- 2d ago First seen · 158 lines · 104 tokens per session scan A cacd915f73ab
postkit-idea is a skill published in the GitHub repository Trystan-SA/postkit (4 stars, last pushed 4mo ago), licensed MIT. It adds 104 tokens to every session and 1,888 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…