Borrowing it
Nothing to install: this file belongs to langfuse/langfuse-docs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/langfuse/langfuse-docs/main/.agents/skills/customer-story-setup/SKILL.mdgit 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/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/langfuse/langfuse-docs/customer-story-setup"><img src="https://agentmods.dev/badge/skills/langfuse/langfuse-docs/customer-story-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 7 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 28 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Memory Poisoning · line 40 Skill attempts to fill the context window with filler content, displacing legitimate instructions and safety constraints. This can degrade agent performance or bypass safety boundaries.Fix: Implement context-window management that detects and rejects padding or stuffing attempts. Prioritize system instructions over user-injected content.
- medium Prompt Injection · line 40 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 42 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 47 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 50 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 53 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.5 | $0.00032 | $0.00849 |
| Sonnet 5.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 2mo 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.
- 2mo 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 (249 stars, last pushed today), licensed MIT. It adds 81 tokens to every session and 2,122 once invoked, about $0.0003 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-08-30.
customer-story-setup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| customer-story-setuplangfuse/langfuse-docs | Skill | 249 | today | MIT | A | 81 | Claude Code, Codex |
| create-atomic-toolEigenwise/atomic-agents | Skill | 6.3k | 8d ago | MIT | A | 99 | Claude Code |
| frameworkEigenwise/atomic-agents | Skill | 6.3k | 8d ago | MIT | A | 74 | Claude Code |
| create-atomic-agentEigenwise/atomic-agents | Skill | 6.3k | 8d ago | MIT | A | 93 | Claude Code |
| create-atomic-context-providerEigenwise/atomic-agents | Skill | 6.3k | 8d ago | MIT | A | 106 | Claude Code |
| create-atomic-schemaEigenwise/atomic-agents | Skill | 6.3k | 8d ago | MIT | A | 89 | Claude Code |
| new-appEigenwise/atomic-agents | Skill | 6.3k | 8d ago | MIT | A | 76 | Claude Code |