story-beginnings-and-endings

story-beginnings-and-endings is a skill for Claude Code from fatihguner/foreman. It costs 102 tokens per session (4,592 once invoked), scanned A, original, MIT.

A storytelling guide about choosing where a story should begin and how it should end. It explains why starting close to the important change can make a pitch, talk, or narrative clearer and more engaging.

In plain words
What is it for?
Use it to revise the first and last parts of presentations, pitches, talks, and written stories. It is also useful when deciding what context to leave out.
Why use it?
It helps fix openings that spend too long on background or endings that resolve too neatly. The guide gives structure when a story feels unfocused or fails to move forward.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the foreman plugin — 142 skills, 60 commands, 7 agents shipped together

Good fit Use it to revise the first and last parts of presentations, pitches, talks, and written stories. It is also useful when deciding what context to leave out.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fatihguner/foreman/story-beginnings-and-endings
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 fatihguner/foreman --skill story-beginnings-and-endings
Clone the repo
git clone --depth 1 https://github.com/fatihguner/foreman

Made for: Claude Code.

Or install foreman, the plugin that ships this one along with the rest of its 142 skills, 60 commands, 7 agents.

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 story-beginnings-and-endings

README.md
[![agentmods](https://agentmods.dev/badge/skills/fatihguner/foreman/story-beginnings-and-endings/github.svg)](https://agentmods.dev/skills/fatihguner/foreman/story-beginnings-and-endings)
Your own site
<a href="https://agentmods.dev/skills/fatihguner/foreman/story-beginnings-and-endings"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/story-beginnings-and-endings/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 story-beginnings-and-endings

Your own site · 80×15
<a href="https://agentmods.dev/skills/fatihguner/foreman/story-beginnings-and-endings"><img src="https://agentmods.dev/badge/skills/fatihguner/foreman/story-beginnings-and-endings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 102 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,592 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found 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.00102 $0.04592
Opus 5 $0.00051 $0.02296
Sonnet 5 $0.00020 $0.00918
Haiku 4.5 $0.00010 $0.00459

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

Security

Grade A, and why

story-beginnings-and-endings 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 6d 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.

plugins/foreman/skills/story-beginnings-and-endings/SKILL.md · 231 lines

How it starts

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

Read runtime and advisory rules before applying this skill. Other Foreman layers and the catalog are in ../../content/, relative to this SKILL.md.

Story Beginnings and Endings

BACKWARDS -- Good stories are built backwards from the ending. Most storytellers do not know this, which is why they start in the wrong place.

More than half the crafting time should go to a single decision: where to begin. Not on the climax. Not on the emotional payload. Not on the jokes or the vivid details. On the first sentence. This allocation of effort is counterintuitive and, according to the framework, the single most consequential craft decision a storyteller makes. The ending -- the five-second moment of transformation -- is given. It happened. The storyteller knows what changed. The beginning, by contrast, must be chosen from an ocean of possibilities, and most storytellers choose poorly.

The error is almost always the same: starting too early. The founder who opens a pitch with her childhood. The CEO who begins a company narrative with the founding date. The speaker who spends three minutes establishing context before arriving at anything that matters. They start too early because they confuse chronology with story. A story is not a timeline. A story is an arc from one state of being to its opposite, and the beginning must be selected to create that arc -- not to provide a comprehensive history.

Endings suffer from the inverse problem. Where beginnings err by starting too early, endings err by going too late -- wrapping up, explaining, moralising, restating the point. The best endings, the framework argues, do not land neatly. They fray. They connect back to the beginning with transformed meaning, leaving the audience to feel the resonance rather than having it explained to them.


The Framework

Finding the Beginning: The Opposite-of-the-End Rule

The process starts at the end. The five-second moment of transformation is the story's destination. Once it is identified, the beginning reveals itself through a single question: What is the opposite of my ending?

Read the full file on GitHub · 231 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. 6d ago First seen · 231 lines · 102 tokens per session scan A 4a769a861f53

Subscribe to this mod's changes

story-beginnings-and-endings is a skill published in the GitHub repository fatihguner/foreman (50 stars, last pushed 7d ago), licensed MIT. It adds 102 tokens to every session and 4,592 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-09-06.