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 agentmods add skills/is-bo/fullstack-forge-skill/data-storytellingnpx skills add is-bo/fullstack-forge-skill --skill data-storytellinggit clone --depth 1 https://github.com/is-bo/fullstack-forge-skillWrote 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/is-bo/fullstack-forge-skill/data-storytelling)<a href="https://agentmods.dev/skills/is-bo/fullstack-forge-skill/data-storytelling"><img src="https://agentmods.dev/badge/skills/is-bo/fullstack-forge-skill/data-storytelling.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.00034 | $0.00451 |
| Opus 5 | $0.00017 | $0.00226 |
| Sonnet 5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
data-storytelling 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 2d 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.
This is a copy
100% identical to data-storytelling — 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.
What it actually says
Data Storytelling
Transform raw data into compelling narratives that drive decisions and inspire action.
When to Use This Skill
- Presenting analytics to executives
- Creating quarterly business reviews
- Building investor presentations
- Writing data-driven reports
- Communicating insights to non-technical audiences
- Making recommendations based on data
Core Concepts
1. Story Structure
Setup → Conflict → Resolution
Setup: Context and baseline
Conflict: The problem or opportunity
Resolution: Insights and recommendations
2. Narrative Arc
1. Hook: Grab attention with surprising insight
2. Context: Establish the baseline
3. Rising Action: Build through data points
4. Climax: The key insight
5. Resolution: Recommendations
6. Call to Action: Next steps
3. Three Pillars
| Pillar | Purpose | Components |
|---|---|---|
| Data | Evidence | Numbers, trends, comparisons |
| Narrative | Meaning | Context, causation, implications |
| Visuals | Clarity | Charts, diagrams, highlights |
Detailed patterns and worked examples
Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.
Best Practices
Do's
- Start with the "so what" - Lead with insight
- Use the rule of three - Three points, three comparisons
- Show, don't tell - Let data speak
- Make it personal - Connect to audience goals
- End with action - Clear next steps
Don'ts
- Don't data dump - Curate ruthlessly
- Don't bury the insight - Front-load key findings
- Don't use jargon - Match audience vocabulary
- Don't show methodology first - Context, then method
- Don't forget the narrative - Numbers need meaning
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.
- 2d ago First seen · 71 lines · 34 tokens per session scan A 0244a9ef6bca
data-storytelling is a skill published in the GitHub repository is-bo/fullstack-forge-skill (2 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 451 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to data-storytelling, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
architecture-decision-records
Comprehensive patterns for creating, maintaining, and managing Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions.
bugcrowd-reporting
Bugcrowd-specific reporting tactics complementing report-writing: VRT category search-and-fallback strategy when no exact match exists, manual severity override when VRT defaults underrate impact, severity-request paragraph as first body section, OOS-clause rebuttal templates (rate limiting on auth-flow endpoints…
peon-ping-log
Log exercise reps for the Peon Trainer. Use when user says they did pushups, squats, or wants to log reps. Examples - "/peon-ping-log 25 pushups", "/peon-ping-log 30 squats", "log 50 pushups".
conductor-implement
Executes the tasks defined in the specified track's plan. Use this to start or continue working on a feature, bug fix, or chore.
autonomous-agent-patterns
Design patterns for building autonomous coding agents, inspired by Cline and OpenAI Codex.
godot-signals-groups
Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and callgroup. Use when wiring node communication in a Godot project, replacing tight references with signals…