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.
git clone --depth 1 https://github.com/langfuse/skillsWrote 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/plugins/langfuse/skills/skills)<a href="https://agentmods.dev/plugins/langfuse/skills/skills"><img src="https://agentmods.dev/badge/plugins/langfuse/skills/skills/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/plugins/langfuse/skills/skills"><img src="https://agentmods.dev/badge/plugins/langfuse/skills/skills.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
langfuse 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 11d 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.
What it actually says
{
"name": "langfuse",
"description": "Skills for working with Langfuse, the open-source LLM engineering platform for tracing, prompt management, and evaluation.",
"version": "1.11.0",
"author": {
"name": "Langfuse",
"email": "[email protected]"
},
"homepage": "https://langfuse.com",
"repository": "https://github.com/langfuse/skills",
"license": "MIT",
"keywords": [
"langfuse",
"llm",
"observability",
"tracing",
"prompt-management",
"evaluation"
]
}
What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 282 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 11d ago Changed 3984bd35fd75
- 27d ago Changed 3997ce20c868
- 28d ago Changed 26c1c7079679
- 1mo ago Changed a4f6a884c681
- 1mo ago Changed cad6baa2d2a7
- 1mo ago Changed 7f5e6297a5d9
- 1mo ago Changed e64e197899d4
- 1mo ago Changed 7067818e43e7
- 1mo ago First seen · 21 lines scan A 7345e58b645d
langfuse is a plugin published in the GitHub repository langfuse/skills (319 stars, last pushed yesterday), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
developer-kit-ai
AI/ML capabilities including prompt engineering, RAG, and chunking strategies.
experiment-tracker
ML experiment tracking with metrics logging and run comparison.
git-tools
Git workflow skills — worktrees for parallel, conflict-free work on multiple branches.
famulor-assistants-history
Review Famulor assistants and read omnichannel call, messaging, and email history through an OAuth-secured, read-only 11-tool MCP profile.
beeyev-skills
Agent skills by beeyev: GitLab CI/CD pipelines and more.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.