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 oborchers/fractional-cto --skill narrative-craftgit clone --depth 1 https://github.com/oborchers/fractional-ctoWrote 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/oborchers/fractional-cto/narrative-craft)<a href="https://agentmods.dev/skills/oborchers/fractional-cto/narrative-craft"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/narrative-craft/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/oborchers/fractional-cto/narrative-craft"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/narrative-craft.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.00080 | $0.02235 |
| Opus 5.5 | $0.00032 | $0.00894 |
| Sonnet 5.5 | $0.00016 | $0.00447 |
| Haiku 4.5 | $0.00008 | $0.00224 |
Grade A, and why
narrative-craft 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 5d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Narrative Craft
Overview
Guide the retell pipeline's LLM stages through editorial decisions: which moments matter, what angle to take, how to structure beats, and how to write in authentic first-person voice. This skill provides the narrative principles and practical heuristics for the Triage, Outline, Draft, and Polish stages.
Hard Constraints
First-Person Voice
All blog posts use first-person voice from the author's perspective. This is not configurable.
- "I asked Claude to..." not "The user asked Claude to..."
- "I rejected the monochrome direction because..." not "Oliver rejected..."
- "I'd built this brainstorming skill the week before..." not "A brainstorming skill had been built..."
No Dashes as Punctuation
Never use em dashes, en dashes, or hyphens as punctuation in the final blog post. They are a dead giveaway of AI-generated text. Restructure sentences instead: use commas, semicolons, colons, parentheses, or split into separate sentences. Hyphens in compound words (e.g., "real-time", "well-known") are fine.
Output Language
The blog post can be written in English or German, configured at the triage gate. The language setting affects all text output: section headings, prose, quotes, and revisions.
Language-independent rules:
- First-person voice applies in both languages ("I asked..." / "Ich fragte...")
- The no-dashes-as-punctuation rule applies regardless of language
- Quote handling rules apply regardless of language (clean typos, merge fragments, never fabricate)
Quote translation: When the output language differs from the conversation language, translate all quotes into the output language so the entire post reads consistently in one language. Preserve the speaker's tone and emotional register in translation.
German-specific guidance:
- Use natural German prose, not translated English. "Ich bat Claude, die Architektur zu analysieren" not "Ich fragte Claude zu analysieren die Architektur."
- First-person voice: "Ich verwarf den ersten Entwurf, weil..." not "Der Autor verwarf..."
- Technical terms that are conventionally used in English in the German tech community may stay in English: "Pull Request," "Deployment," "Refactoring." Do not force German translations of established terms.
- If a style reference is in English, extract structural patterns (paragraph rhythm, header density, humor level, sentence length distribution) and apply them to German prose. Do not translate the reference; borrow its voice architecture.
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.
- 5d ago First seen · 201 lines · 80 tokens per session scan A 076dd916b4dc
narrative-craft is a skill published in the GitHub repository oborchers/fractional-cto (32 stars, last pushed 5d ago), licensed MIT. It adds 80 tokens to every session and 2,235 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-10-13.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.