Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/DorianSchlede/nexus-templatenpx agentmods add skills/dorianschlede/nexus-template/langfuse-connectWrote 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/dorianschlede/nexus-template/langfuse-connect)<a href="https://agentmods.dev/skills/dorianschlede/nexus-template/langfuse-connect"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/langfuse-connect/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/dorianschlede/nexus-template/langfuse-connect"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/langfuse-connect.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.00017 | $0.03041 |
| Opus 5 | $0.00009 | $0.01520 |
| Sonnet 5 | $0.00003 | $0.00608 |
| Haiku 4.5 | $0.00002 | $0.00304 |
Grade A, and why
langfuse-connect scanned grade A with 1 finding 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.
Asks the agent to reveal its instructionslowSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
| "get prompt {name}", "show prompt" | langfuse-get-prompt | GET /v2/prompts/{name} | Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Langfuse Connect
User-facing entry point for Langfuse integration. Routes to appropriate operation skills.
Context Reference
For score config IDs, trace structure, and API patterns, load:
uv run python 00-system/core/nexus-loader.py --skill langfuse-help
Pre-Flight Check (ALWAYS FIRST)
Before any operation, run config check:
uv run python 00-system/skills/langfuse/langfuse-master/scripts/check_langfuse_config.py --json
If ai_action is:
proceed_with_operation→ Continue with requested operationprompt_for_api_key→ Ask user for credentials, guide to setup
Routing Table
Core Operations (Project 08)
| User Says | Skill to Load | Endpoint |
|---|---|---|
| "list traces", "show traces", "get traces" | langfuse-list-traces | GET /traces |
| "get trace {id}", "trace details" | langfuse-get-trace | GET /traces/{id} |
| "list observations", "show spans" | langfuse-list-observations | GET /v2/observations |
| "get observation {id}" | langfuse-get-observation | GET /observations/{id} |
| "list sessions", "show sessions" | langfuse-list-sessions | GET /sessions |
| "get session {id}" | langfuse-get-session | GET /sessions/{id} |
| "list scores", "show evaluations" | langfuse-list-scores | GET /v2/scores |
| "get score {id}" | langfuse-get-score | GET /v2/scores/{id} |
| "list models", "model costs" | langfuse-list-models | GET /models |
| "get model {id}" | langfuse-get-model | GET /models/{id} |
| "get project", "current project" | langfuse-get-project | GET /projects |
Prompts (Phase 1)
| User Says | Skill to Load | Endpoint |
|---|---|---|
| "list prompts", "show prompts" | langfuse-list-prompts | GET /v2/prompts |
| "create prompt", "new prompt" | langfuse-create-prompt | POST /v2/prompts |
| "get prompt {name}", "show prompt" | langfuse-get-prompt | GET /v2/prompts/{name} |
| "delete prompt", "remove prompt" | langfuse-delete-prompt | DELETE /v2/prompts/{name} |
| "update prompt", "set prompt label" | langfuse-update-prompt-version | PATCH /v2/prompts/{name}/versions/{v} |
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 · 315 lines · 17 tokens per session scan A 3f30a7bb7dfc
langfuse-connect is a skill published in the GitHub repository DorianSchlede/nexus-template (8 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 3,041 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…