writing-fragments

writing-fragments is a skill for Claude Code, Codex from klimentij/klimkit. It costs 80 tokens per session (723 once invoked), scanned A, a copy of writing-fragments, MIT.

A writing-session tool that collects raw pieces of a future article, such as claims, examples, sharp sentences, and unfinished thoughts. It stores those pieces in one Markdown document while the ideas are being developed.

In plain words
What is it for?
Brainstorming an article, gathering notes and fragments during an interview, and building source material before organizing it into a finished structure.
Why use it?
It lets the writer explore ideas without forcing them into an outline too early. The shared document preserves the growing material and the writer's own edits.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Brainstorming an article, gathering notes and fragments during an interview, and building source material before organizing it into a finished structure.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/klimentij/klimkit/writing-fragments
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.

Any agent
npx skills add klimentij/klimkit --skill writing-fragments
Clone the repo
git clone --depth 1 https://github.com/klimentij/klimkit

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for writing-fragments

README.md
[![agentmods](https://agentmods.dev/badge/skills/klimentij/klimkit/writing-fragments/github.svg)](https://agentmods.dev/skills/klimentij/klimkit/writing-fragments)
Your own site
<a href="https://agentmods.dev/skills/klimentij/klimkit/writing-fragments"><img src="https://agentmods.dev/badge/skills/klimentij/klimkit/writing-fragments/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.

agentmods 80×15 button for writing-fragments

Your own site · 80×15
<a href="https://agentmods.dev/skills/klimentij/klimkit/writing-fragments"><img src="https://agentmods.dev/badge/skills/klimentij/klimkit/writing-fragments.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 723 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.1 $0.00080 $0.00723
Opus 5 $0.00040 $0.00362
Sonnet 5 $0.00016 $0.00145
Haiku 4.5 $0.00008 $0.00072

Measured 9d ago against content hash 4ffa34a701ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

writing-fragments 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 9d 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

This is a copy

100% identical to writing-fragments — 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.

third_party/mattpocock-skills/skills/in-progress/writing-fragments/SKILL.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Run a grilling session that produces fragments. Interview the user relentlessly about whatever they want to write about. Do not impose phases, outlines, or structure — that is explicitly out of scope.

As fragments emerge from either side of the conversation, append them to a single markdown file. The user will be editing this file during the session; always re-read it before writing so their edits are preserved.

If the user did not pass a path, ask once where to save the document, then remember it for the rest of the session.

Capture fragments from the very first thing the user says, including the initial prompt.

On first write, put a single H1 at the top with a working title (it can change later) and nothing else — no metadata, no TOC, no date.

What is a fragment

A fragment is any piece of text that might survive into the final article. It must be readable by the author — the author can tell what it means — but it does not need to define its terms or be comprehensible to a cold reader. The bar is "is this a piece of good writing?", not "is this a self-contained argument?"

Fragments are deliberately heterogeneous. Examples of what could be a fragment:

  • A sharp sentence you'd want to deploy somewhere but don't yet know where.
  • A claim with a one-line justification.
  • A vignette: a thing that happened, a code snippet, a scenario, an analogy.
  • A half-thought: "something about how X feels like Y, work this out later."
  • A quote, a piece of dialogue, an overheard line.
  • A list of related observations that hang together by feel.
  • A complaint, a confession, a punchline.

The novelist's diary is the model: years of unstructured noticings that later get mined for raw material. Fragments are noticings.

File format

# Working title

A first fragment lives here.

It can be multiple paragraphs. It can include lists, code, quotes — whatever
shape the fragment naturally takes.

---

A second fragment.

---

> A quoted line that the user wants to keep around.

A reaction to it.

---

- A cluster of related observations
- That hang together by feel
- And want to be near each other

Read the full file on GitHub · 76 lines

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. 9d ago First seen · 76 lines · 80 tokens per session scan A 4ffa34a701ca

Subscribe to this mod's changes

writing-fragments is a skill published in the GitHub repository klimentij/klimkit (7 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 723 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to writing-fragments, differing in 0 lines, and is treated as a copy.