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 glebis/humane-agentic-design --skill narrative-scrollytellinggit clone --depth 1 https://github.com/glebis/humane-agentic-designWrote 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/glebis/humane-agentic-design/narrative-scrollytelling)<a href="https://agentmods.dev/skills/glebis/humane-agentic-design/narrative-scrollytelling"><img src="https://agentmods.dev/badge/skills/glebis/humane-agentic-design/narrative-scrollytelling/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/glebis/humane-agentic-design/narrative-scrollytelling"><img src="https://agentmods.dev/badge/skills/glebis/humane-agentic-design/narrative-scrollytelling.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.00117 | $0.01197 |
| Opus 5.5 | $0.00047 | $0.00479 |
| Sonnet 5.5 | $0.00023 | $0.00239 |
| Haiku 4.5 | $0.00012 | $0.00120 |
Grade A, and why
narrative-scrollytelling 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 1mo 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Narrative Scrollytelling
Announce at start: "I'm using the humane:narrative-scrollytelling skill to turn this sequence into a scroll story that remains a readable document."
Scrollytelling is a document before it is choreography. The ordered ideas, headings, prose and media alternatives form a complete canonical reading order; scroll position may change their presentation, never their existence or meaning.
Quick reference
| Need | Read |
|---|---|
| Story shapes, drivers, sticky stages and pacing | references/patterns.md |
| The story-map fields and fallback invariants | references/contract.md |
Build the story map
- Establish the ordered beats outside the visual treatment. Each beat carries one claim or change in understanding and a stable id.
- Choose the least demanding driver that expresses the relationship:
discrete-intersectionfor prose steps,view-progressfor a visual whose change follows its visibility, andscroll-progressonly when intermediate states themselves communicate meaning. - Decide what remains in normal document flow and what may be sticky. A sticky visual stage is normally non-focusable; interactive content stays in logical source order.
- Specify navigation and fallbacks before transition polish: anchors, previous/next where useful, skip-story, no-JavaScript, reduced-motion, no-motion and unsupported-driver behavior.
- Only then name transition intents and token references.
Write the result using references/contract.md. When the user wants a saved
artifact, resolve artifact_path(name, "narrative-scrollytelling", "json");
never assemble a .design path at the call site. Validate a saved map with
python3 scripts/validate_map.py <map.json>.
Hard boundaries
steps[]order is canonical DOM and reading order. Every essential fact is present as semantic content outside canvas frames, keyframes and transition labels.- Native page scrolling remains in control. Do not hijack wheel/touch input, lock the reader into a scene, require scroll speed/direction, or turn the document into an inaccessible slide deck.
- Scrolling does not move focus or announce every step. Sticky authored content cannot obscure focused controls; reserve safe offsets and scroll padding.
- Default snap is
none;proximityis optional.mandatoryrequires an explicit audited exception proving all content remains reachable at zoom, reflow, large text and short viewports. - Reduced motion removes parallax, scrubbed spatial travel, smooth scrolling and long pinning. The fallback uses discrete static states or the linear document; meaning never depends on an exact progress fraction.
- No-JavaScript and unsupported-feature modes expose the whole story. Native CSS scroll timelines are progressive enhancement, not a prerequisite.
- Continuous automatically started movement is absent by default. If an essential presentation exceeds five seconds alongside other content, provide pause, stop or hide controls and name the reason.
What ships with it
5 files 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.
- 1mo ago First seen · 104 lines · 117 tokens per session scan A 88574aa3957b
narrative-scrollytelling is a skill published in the GitHub repository glebis/humane-agentic-design (36 stars, last pushed today), licensed MIT. It adds 117 tokens to every session and 1,197 once invoked, about $0.0005 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-09-11.
Other skills, from other repositories
figma-extract-design-system
Extract a design system from vibe-coded production apps that never had one: inventory components, mine de-facto styling into DTCG tokens, scaffold a Storybook package, port components, and optionally round-trip tokens/components into Figma. Use when the user wants to 'extract a design system', 'create a design system…
figma-blame-node
Find which Figma version introduced a specific change — a component property or a child node — via a binary search over version history (log2(N) API calls instead of N). Answers 'who added this and when'. Use when the user wants git-blame-style attribution for a Figma design — triggers: 'when was this component…
figma-generate-component-doc
Generate complete Markdown documentation for a Figma component — anatomy/layer tree, design tokens (colors, spacing, typography), states/variants matrix, accessibility notes, content guidelines, and optional code-parity + YAML frontmatter. Use when the user wants a docs page or handoff spec for a component or…
figma-version-history
List a Figma file's version history, snapshot the file at any past version, and diff two versions (added/removed/renamed pages plus deep per-component changes). Use when the user wants to inspect Figma history — triggers: 'list Figma versions', 'what versions does this file have', 'show version history', 'snapshot…
figma-comments
Read, post, reply to, and delete comments on a Figma file via the REST API — including pinning a comment to a specific node and threading replies. Use when the user wants to work with Figma comments programmatically — triggers: 'get Figma comments', 'read comments on this file', 'post a comment in Figma', 'leave a…
figma-export-tokens
Export Figma variables to design token files in DTCG, CSS custom properties, Tailwind v4/v3, SCSS, TypeScript, JSON, Style Dictionary, or Tokens Studio. Use when the user wants to pull design tokens OUT of Figma into code — triggers: 'export tokens', 'export Figma variables', 'generate CSS variables from Figma', 'turn…