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 SZoloth/skill-pack --skill storytelling-influencegit clone --depth 1 https://github.com/SZoloth/skill-packWrote 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/szoloth/skill-pack/storytelling-influence)<a href="https://agentmods.dev/skills/szoloth/skill-pack/storytelling-influence"><img src="https://agentmods.dev/badge/skills/szoloth/skill-pack/storytelling-influence/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/szoloth/skill-pack/storytelling-influence"><img src="https://agentmods.dev/badge/skills/szoloth/skill-pack/storytelling-influence.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.00121 | $0.01322 |
| Opus 5 | $0.00060 | $0.00661 |
| Sonnet 5 | $0.00024 | $0.00264 |
| Haiku 4.5 | $0.00012 | $0.00132 |
Grade A, and why
storytelling-influence 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Storytelling, communication, and influence coach
Apply the techniques in reference.md to improve the user's storytelling, communication, and influence. The reference contains 45 techniques organized into three domains, each with named sources. Use them as a coaching toolkit, not a checklist to recite.
How to use this skill
Mode 1: Review and improve a draft
When the user shares a draft (presentation, email, Slack message, document, pitch):
- Identify the 2-3 most impactful techniques from the reference that apply
- Diagnose the specific gap (not generic praise)
- Rewrite the weak sections applying the techniques, citing which one you used
- Run the relevant checklist from the reference against the final version
Storytelling gaps to check:
- Is the audience positioned as the hero, or is the author?
- Does it open in the middle of the action, or with preamble?
- Is there a single memorable "meme" the reader walks away with?
- Does it compel a specific action?
Communication gaps to check:
- Could the first paragraph be cut entirely?
- Is the point of view "spiky" — or could anyone write this?
- Does it start with chapter one (strategy context) for execs?
- Are there minimizing qualifiers (just, actually, quickly, sorry)?
Influence gaps to check:
- Is the ask framed around THEIR goals, not yours?
- Is there evidence in priority order (data > research > anecdotes)?
- Has the "meeting before the meeting" been done?
- Is there a concrete desired outcome stated?
Mode 2: Prep for a stakeholder conversation
When the user is preparing for a meeting, pitch, or difficult conversation:
- Ask who the audience is and what decision they need
- Pull the relevant influence techniques from the reference:
- Stakeholder intel gathering (3.8)
- Frame from their POV (3.9)
- Meeting before the meeting (3.10)
- Make people feel heard (3.11)
- Manage the clock (3.12)
- Help the user build a prep sheet:
- Each stakeholder's goals and concerns
- How the ask maps to their goals
- Anticipated objections and rebuttals
- Champions to activate
- Concrete desired outcome + time allocation
- If relevant, apply the sales pitch structure (3.18): insight → alternatives → perfect world → differentiated value
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.
- 9d ago First seen · 130 lines · 121 tokens per session scan A 265e153f7e62
storytelling-influence is a skill published in the GitHub repository SZoloth/skill-pack (14 stars, last pushed 5mo ago), licensed MIT. It adds 121 tokens to every session and 1,322 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-30.
Other skills, from other repositories
claudeshrink
Automatically compress large natural text or log files before processing. Trigger when the user pastes massive text blobs, or asks to analyze a large file (logs, docs, transcripts), or provides a prompt that is too large for the context window. DO NOT trigger on source code files or structural data (JSON, XML).
draft-plan
Produce an implementation plan at .turbo/plans/ .md. Use when the user asks to "draft a plan", "draft the plan", "write an implementation plan", "plan this change", "create an implementation plan", or needs a first-draft plan file before refinement.
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…
smoke-test
Launch the app and hands-on verify that it works by interacting with it. Falls back to an existing integration test suite when there is no interactive surface in scope. Use when the user asks to "smoke test", "test it manually", "verify it works", "try it out", "run a smoke test", "check it in the browser", or "does…
consult-codex
Multi-turn consultation with Codex CLI for second opinions, brainstorming, or collaborative problem-solving. Use when the user asks to "consult codex", "ask codex", "get codex's opinion", "brainstorm with codex", "discuss with codex", or "chat with codex".
exploratory-test
Execute multi-level exploratory testing of the app covering basic functionality, complex operations, adversarial testing, and cross-cutting scenarios, plus usability observations through a UX lens reported separately from defects. Deeper than /smoke-test. Use when the user asks to "exploratory test", "test…