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 Trystan-SA/postkit --skill postkit-setupgit clone --depth 1 https://github.com/Trystan-SA/postkitWrote 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/trystan-sa/postkit/postkit-setup)<a href="https://agentmods.dev/skills/trystan-sa/postkit/postkit-setup"><img src="https://agentmods.dev/badge/skills/trystan-sa/postkit/postkit-setup/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/trystan-sa/postkit/postkit-setup"><img src="https://agentmods.dev/badge/skills/trystan-sa/postkit/postkit-setup.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.00070 | $0.02273 |
| Opus 5.5 | $0.00028 | $0.00909 |
| Sonnet 5.5 | $0.00014 | $0.00455 |
| Haiku 4.5 | $0.00007 | $0.00227 |
Grade A, and why
postkit-setup 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 1mo 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/postkit-setup — brand intake
You are a friendly brand strategist interviewing the user so future posts consistently sound like them and look like their brand.
Where the answers go
Persist every answer to plain Markdown files in memory/ at the project
root. This folder is the source of truth for the brand profile —
/postkit-new, /postkit-idea, and /postkit-review all read from it.
Do not write brand state into Claude Code's internal memory system for
postkit projects; the user wants brand state versioned with the project.
Organize the brand profile into these files (create them as you fill each topic):
| File | Holds |
|---|---|
memory/brand_identity.md |
Brand name, handles per platform, default handle, what they do, niche, primary language |
memory/brand_audience.md |
Who they talk to, what those people care about, their level |
memory/brand_goals.md |
Primary outcome, primary + secondary platforms, posting frequency |
memory/brand_voice.md |
3 adjectives, do's, don'ts, signature phrases and rituals |
memory/brand_visual.md |
Brand colors (hex), typography, aesthetic keywords, watermark default |
memory/brand_hooks.md |
Hook formulas and off-limits topics |
Each file is plain Markdown — no frontmatter required. Use ## section
headings for each sub-topic so the file stays human-readable when the user
opens it later. Example for memory/brand_identity.md:
# Brand identity
## Brand name
Somanyways
## Handles
- Instagram: @somanyways.co
- TikTok: @somanyways
- Default (watermark): @somanyways
## What we do
Help burned-out designers pivot into product strategy.
## Niche
career coaching
## Primary language
English
Create memory/ if it doesn't exist. The only other file at the project
root you update during setup is theme.css — see step 5.
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.
- 1mo ago First seen · 175 lines · 70 tokens per session scan A 5bffea44bf27
postkit-setup is a skill published in the GitHub repository Trystan-SA/postkit (4 stars, last pushed 5mo ago), licensed MIT. It adds 70 tokens to every session and 2,273 once invoked, about $0.0003 per session on Opus 5.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
claude-reflect
Self-learning system that captures corrections during sessions and reminds users to run /reflect to update CLAUDE.md. Use when discussing learnings, corrections, or when the user mentions remembering something for future sessions.
company-brain
Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede…
second-brain
When you want to capture into, compile, query, lint, or connect your personal Second Brain. Wraps the Karpathy LLM Wiki schema (Obsidian or any markdown vault) — raw/ (unprocessed sources), wiki/ (AI-compiled interlinked topic pages), outputs/ (generated artifacts). Tool-agnostic in design but defaults to a vault at…
self-improve
Extract lessons from the current session, or sweep the project's past sessions when asked, and route them to the appropriate knowledge layer (project AGENTS.md, auto memory, existing skills, or new skills). Use when the user asks to "self-improve", "distill this session", "distill past sessions", "sweep past…
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
compound-docs
Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.