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/add-yourself-to-team-langfuse/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/add-yourself-to-team-langfuse)<a href="https://agentmods.dev/skills/langfuse/langfuse-docs/add-yourself-to-team-langfuse"><img src="https://agentmods.dev/badge/skills/langfuse/langfuse-docs/add-yourself-to-team-langfuse/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/add-yourself-to-team-langfuse"><img src="https://agentmods.dev/badge/skills/langfuse/langfuse-docs/add-yourself-to-team-langfuse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.00569 |
| Opus 5 | $0.00026 | $0.00284 |
| Sonnet 5 | $0.00010 | $0.00114 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
add-yourself-to-team-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 10d 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
Add a new team member to Langfuse. Ask the user for the following information before proceeding:
- Full name (including any special characters, e.g. umlauts)
- Role/title (e.g. "Growth & Developer Relations")
- GitHub username (e.g. from https://github.com/username)
- LinkedIn URL (e.g. https://www.linkedin.com/in/handle/)
- X/Twitter handle (e.g. from https://x.com/handle) — optional
- Profile photo — remind them to add it to
public/images/people/<key>.jpg
Once you have the information, update the following source files:
1. data/authors.json
Add a new entry at the end (before the closing }). Use a lowercase, no-special-chars version of the name as the key (e.g. annabellschafer):
"<key>": {
"firstName": "<first name>",
"name": "<full name>",
"title": "<role>",
"image": "/images/people/<key>.jpg",
"twitter": "<twitter handle>", // omit if not provided
"github": "<github username>", // omit if not provided
"linkedin": "<linkedin handle>" // omit if not provided
}
2. components-mdx/team-members.mdx
This is the canonical website team list. It is rendered by the press, about, careers, and handbook team pages. Append a new table row at the end:
| **<Full Name>** | <Role> | [Twitter](https://x.com/<twitter>), [LinkedIn](https://www.linkedin.com/in/<linkedin>/), [GitHub](https://github.com/<github>) |
Omit any social links that were not provided.
3. Confirm shared usage
Do not add team rows directly to any other page. Those pages should import and render the canonical component:
import TeamMembers from "@/components-mdx/team-members.mdx";
<TeamMembers />
If a page has a hand-written team table or list, replace it with the shared
TeamMembers import instead of adding another copy. Please do a quick search for some team members to confirm that there are no copies of this table.
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.
- 10d ago First seen · 63 lines · 51 tokens per session scan A 78403a6fcadc
add-yourself-to-team-langfuse is a skill published in the GitHub repository langfuse/langfuse-docs (240 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 569 once invoked, about $0.0003 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
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
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.