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 skills add agentscope-ai/QwenPaw-Data --skill bi-ltv-analysisgit clone --depth 1 https://github.com/agentscope-ai/QwenPaw-DataWrote 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/agentscope-ai/qwenpaw-data/bi-ltv-analysis)<a href="https://agentmods.dev/skills/agentscope-ai/qwenpaw-data/bi-ltv-analysis"><img src="https://agentmods.dev/badge/skills/agentscope-ai/qwenpaw-data/bi-ltv-analysis/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/agentscope-ai/qwenpaw-data/bi-ltv-analysis"><img src="https://agentmods.dev/badge/skills/agentscope-ai/qwenpaw-data/bi-ltv-analysis.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.00068 | $0.01526 |
| Opus 5 | $0.00034 | $0.00763 |
| Sonnet 5 | $0.00014 | $0.00305 |
| Haiku 4.5 | $0.00007 | $0.00153 |
Grade A, and why
bi-ltv-analysis 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 13d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bi-ltv-analysis
评估单个用户或用户群体在整个生命周期内创造的收入(或利润),典型用途。
执行步骤
Step 1:准备数据
根据分析任务需求与所给数据结构,明确 LTV 分析涉及的指标,即分析粒度(用户级 / 群体级)、收益口径(如购买、升级等行为产生的收入、利润等)以及生命周期(如时间窗口、某阶段流失率等),将取数结果保存为 CSV。
整理数据为 CSV 格式,采用“分组(用户/群体) × N天(生命周期与收益数据)”,数据应至少包括分析粒度对应的对象列、收益口径对应的收入数据列以及生命周期对应的数据列。
例如,对于用户级的 LTV 分析,分析数据示例如下,
用户ID,事件时间a,收入金额a,事件时间b,收入金额b
1,2025-04-25,26.0,2025-04-26,6.5
2,2025-04-25,6.5,NaN,NaN
对于群体级的 LTV 分析,数据示例如下,
群体类别,a阶段流失率,a阶段收入金额,b阶段流失率,b阶段收入金额
group_1,0.366,26.0,0.121,6.5
group_2,0.253,6.5,0.754,2.0
若上游步骤已产出可用汇总表则直接使用,否则按口径从明细聚合(按用户求和、按队列求和等)。
注意:若数据包含留存率、流失率等指标可以用于 LTV 分析,则统一使用流失率进行计算,若数据中仅包含留存率,则转化为流失率进行 LTV 计算和分析,一般情况,流失率=1-留存率。
Step 2:计算 LTV
LTV 计算公式一:
(LTV = ARPU \times 生命周期)
LTV 计算公式二:
(LTV = ARPU \times \frac{1}{流失率})
ARPU(Average Revenue Per User):单位用户在指定统计范围内的平均收入。若 CSV 中收入列为阶段合计、且另有用户数列,则脚本按 (ARPU = 收入 / 用户数) 计算;若收入列已是人均口径,则无需 --users-col。
群体多阶段(含多列「阶段流失率 + 阶段收入金额」):按阶段顺序,用存活率对收入加权求和:
[ LTV = \sum_{j} 收入_j \times \prod_{k<j}(1 - 流失率_k) ]
方式一:使用脚本
使用 <skill-dir>/scripts/ltv_calc.py 计算 LTV。结果写入 --output-file 指定的 CSV:第一列为输入中的分析对象列(--object-col),第二列为 LTV(默认列名 ltv)。
用户级(观测窗口内各阶段收入累计):
python <skill-dir>/scripts/ltv_calc.py \
--input-file "<输入 CSV 路径>" \
--object-col "用户ID" \
--revenue-cols "收入金额a" "收入金额b" \
--output-file "<输出 CSV 路径>"
群体级(多阶段流失率 + 收入):
python <skill-dir>/scripts/ltv_calc.py \
--input-file "<输入 CSV 路径>" \
--object-col "群体类别" \
--revenue-cols "a阶段收入金额" "b阶段收入金额" \
--churn-cols "a阶段流失率" "b阶段流失率" \
--output-file "<输出 CSV 路径>"
公式一(单列收入 + 生命周期 T):
python <skill-dir>/scripts/ltv_calc.py \
--input-file "<输入 CSV 路径>" \
--object-col "群体类别" \
--revenue-col "a阶段收入金额" \
--users-col "用户数" \
--lifecycle 12 \
--formula lifecycle \
--output-file "<输出 CSV 路径>"
公式二(单列收入 + 单列流失率):
python <skill-dir>/scripts/ltv_calc.py \
--input-file "<输入 CSV 路径>" \
--object-col "群体类别" \
--revenue-col "a阶段收入金额" \
--churn-col "a阶段流失率" \
--formula churn \
--output-file "<输出 CSV 路径>"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 13d ago First seen · 124 lines · 68 tokens per session scan A bb8738dcf9fa
bi-ltv-analysis is a skill published in the GitHub repository agentscope-ai/QwenPaw-Data (73 stars, last pushed 2d ago), licensed Apache-2.0. It adds 68 tokens to every session and 1,526 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
fastapi-patterns
FastAPI patterns for async APIs, dependency injection, Pydantic request and response models, OpenAPI docs, tests, security, and production readiness.
mem0-tour
Browses all stored memories grouped by category with full content display. Use when reviewing all project memories, exploring stored knowledge, onboarding to a project, or getting an overview of captured decisions, conventions, and learnings.
status
Show whether Mem0 memory is working in this repository, covering configuration, capture state, pending flushes, and whether the Mem0 API key is valid. Use when the user asks whether memory is on, why a memory is missing, or anything looks broken.
pause
Pause Mem0 memory capture on this machine. Use when the user wants to stop memories being recorded, for example for private work or experiments.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…