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/langfuse/langfuse-docs/customer-story-setupnpx skills add langfuse/langfuse-docs --skill customer-story-setupgit clone --depth 1 https://github.com/langfuse/langfuse-docsWrote 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/langfuse/langfuse-docs/customer-story-setup)<a href="https://agentmods.dev/skills/langfuse/langfuse-docs/customer-story-setup"><img src="https://agentmods.dev/badge/skills/langfuse/langfuse-docs/customer-story-setup.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.00081 | $0.02122 |
| Opus 5 | $0.00041 | $0.01061 |
| Sonnet 5 | $0.00016 | $0.00424 |
| Haiku 4.5 | $0.00008 | $0.00212 |
Grade A, and why
customer-story-setup 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Single source of truth: maintain this skill under
.agents/skills/customer-story-setup/only. Claude and Cursor load projected copies under.claude/skills/customer-story-setupand.cursor/skills/customer-story-setup.
Customer story setup (MD -> MDX)
Turns a plain Markdown draft into content/customers/<slug>.mdx in the
same pattern as content/customers/canva.mdx and cresta.mdx.
Before writing any file: collect missing input
Do not guess. If any item below is missing from the user's draft or message, ask explicitly and wait for answers (or confirm defaults).
Content & publishing
| Topic | Ask |
|---|---|
| Company name | Legal/marketing name for copy and quotes |
| Company website | Public URL for the [Company](https://...) link in About <Company> |
| Slug | Filename: <slug>.mdx (lowercase, hyphens), e.g. cresta -> cresta.mdx |
| Page title | H1 string for BlogHeader + YAML title (often "How <Company> ... with Langfuse") |
| Short description | YAML description + BlogHeader description (SEO/social; 1-2 sentences) |
| Publish date | YAML date + BlogHeader date (e.g. March 26, 2026) |
| OG image | Optional ogImage: path; if unset, leave empty like other stories |
Authors (BlogHeader authors={["..."]})
| Topic | Ask |
|---|---|
| Byline author(s) | Who should appear under the title (keys from data/authors.json) |
| External / guest speaker | If not in authors.json: collect name, title, optional socials, and headshot path under public/images/people/ or public/images/customers/<slug>/, then add an entry to data/authors.json (see existing entries). Every authors key must resolve in authors.json. |
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 · 172 lines · 81 tokens per session scan A 87fd62a49697
customer-story-setup is a skill published in the GitHub repository langfuse/langfuse-docs (240 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 2,122 once invoked, about $0.0004 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
create-atomic-tool
Build a BaseTool[InSchema, OutSchema] subclass — input/output schemas, BaseToolConfig, run() (and optional runasync()), env-driven secrets, typed failure outputs. Use when the user asks to "add a tool", "create a tool", "wrap an API as a tool", "build a BaseTool", "make a calculator/search/weather tool", or runs…
framework
Guide for the Atomic Agents Python framework — schemas, agents, tools, context providers, prompts, orchestration, and provider configuration. Use when code imports from atomicagents, defines an AtomicAgent, BaseTool, or BaseIOSchema, or the user asks about multi-agent orchestration or LLM-provider wiring in an…
create-atomic-agent
Build and wire an AtomicAgent[InSchema, OutSchema] — schemas, AgentConfig, SystemPromptGenerator, provider client, history, hooks, optional context providers. Use when the user asks to "create an agent", "add another agent", "build an AtomicAgent", "wire up an agent", "make a planner/router/extractor agent", or runs…
create-atomic-context-provider
Build a BaseDynamicContextProvider that injects a named, titled block into an agent's system prompt at every run() — current time, user identity, retrieved RAG docs, session state, cached DB schema. Use when the user asks to "add a context provider", "inject X into the prompt", "give the agent dynamic context", "wire…
new-app
Scaffold a new Atomic Agents project from scratch — create the directory, pyproject.toml, env file, first agent, and a runnable entry point. Use when the user asks to start a new atomic-agents project from scratch, says "scaffold" / "new project" / "start from zero", or runs /atomic-agents:new-app.
create-atomic-schema
Design and write a BaseIOSchema input/output pair for an Atomic Agents agent or tool — docstrings, field descriptions, validators, error variants. Use when the user asks to "create a schema", "design the input/output schema", "define an IOSchema", "write a BaseIOSchema", "model the agent's output", or runs…