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 vidhunnan/agentic-skills --skill post-exportgit clone --depth 1 https://github.com/vidhunnan/agentic-skillsWrote 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/vidhunnan/agentic-skills/post-export)<a href="https://agentmods.dev/skills/vidhunnan/agentic-skills/post-export"><img src="https://agentmods.dev/badge/skills/vidhunnan/agentic-skills/post-export.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.1 | $0.00111 | $0.02944 |
| Opus 5 | $0.00056 | $0.01472 |
| Sonnet 5 | $0.00022 | $0.00589 |
| Haiku 4.5 | $0.00011 | $0.00294 |
Grade A, and why
post-export 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 7d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
post-export
The skill in this family that is not about posting. It captures the material a post gets built from, on the day it happens.
The record answers what shipped and why it was chosen. It does not hold the third attempt that failed and why, what the flow looked like before it was fixed, or the output of the run that broke. Those are the parts a reader finds interesting, they are freshest the day the work happens, and they are effectively gone a fortnight later when someone sits down to write.
One loss is worse because it is irreversible. Git holds the before-state of code. It holds nothing of the rendered before — the screenshot of the old flow, the doc as it read last week, the failing terminal output. Those are overwritten, and only something running at that moment can catch them.
Three rules govern this skill:
- Never invent a learning. Asked what a session taught, a model supplies a
plausible lesson. Most stretches of work teach nothing crisp, and
*(nothing conclusive)*is a real, useful entry. A backlog full of manufactured insight is worse than an empty one, because the empty one doesn't lie. - It competes with the work it captures, and loses. Any structure demanded in the moment is structure you will not get. So interjection mode writes and gets out of the way; typing happens later.
- It is not a handoff. A handoff is state-oriented and complete — everything the receiver needs, dull parts included. An export is reader-oriented and selective — only what someone who wasn't there would find interesting. A handoff that omits boring-but-necessary context is broken; an export that includes it is useless.
Instructions
Step 0 — Detect your surface
Using Bash availability:
- Claude Code — Bash works and there's a real filesystem. Full flow, including snapshots and retrieval.
- Claude.ai — no filesystem. Run the capture conversationally and emit each item as a downloadable artifact. Say plainly that retrieval is unavailable and that you cannot know the next item number, so the user must set it. Never guess a number — a duplicate item number is worse than an unnumbered one. Skip snapshots and say why.
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.
- 7d ago First seen · 235 lines · 111 tokens per session scan A decd91a31726
post-export is a skill published in the GitHub repository vidhunnan/agentic-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 111 tokens to every session and 2,944 once invoked, about $0.0006 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.