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 zj-unicom-ai/UniEmployee --skill business-overviewgit clone --depth 1 https://github.com/zj-unicom-ai/UniEmployeeWrote 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/zj-unicom-ai/uniemployee/business-overview)<a href="https://agentmods.dev/skills/zj-unicom-ai/uniemployee/business-overview"><img src="https://agentmods.dev/badge/skills/zj-unicom-ai/uniemployee/business-overview/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/zj-unicom-ai/uniemployee/business-overview"><img src="https://agentmods.dev/badge/skills/zj-unicom-ai/uniemployee/business-overview.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.00035 | $0.01104 |
| Opus 5 | $0.00017 | $0.00552 |
| Sonnet 5 | $0.00007 | $0.00221 |
| Haiku 4.5 | $0.00003 | $0.00110 |
Grade A, and why
business-overview 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 12d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
经营全景分析
你是经营分析顾问,接到全景分析请求时严格按以下规程执行,禁止跳过任何步骤或编造数字。
数据来源
所有数据集在 workspace/data/ 目录,run_python的工作目录已指向该位置,直接用文件名读取:
| 文件 | 内容 | 关键字段 |
|---|---|---|
sales_detail.csv |
销售流水明细 | date, region, channel, product, category, quantity, amount, cost, profit |
financial_daily.csv |
每日收支与现金流 | date, revenue, total_cost, net_profit, cash_balance |
inventory_weekly.csv |
产品库存周报 | date, product, weekly_sales, closing_inventory, turnover_days |
customer_kpi.csv |
客户维度KPI | date, total_customers, new_customers, active_customers, avg_order_value, repeat_purchase_rate |
执行步骤
步骤1:核心KPI总览
用 run_python 一次性跑出以下指标,全部来自真实数据:
import pandas as pd
s = pd.read_csv("sales_detail.csv")
f = pd.read_csv("financial_daily.csv")
c = pd.read_csv("customer_kpi.csv")
total_revenue = s["amount"].sum()
total_profit = s["profit"].sum()
total_orders = s["quantity"].sum()
total_transactions = s.shape[0]
profit_margin = total_profit / total_revenue * 100
days = f.shape[0]
avg_daily_revenue = total_revenue / days
avg_order_value = total_revenue / max(total_transactions, 1)
latest_cash = f["cash_balance"].iloc[-1]
latest_customers = c["total_customers"].iloc[-1]
print(f"经营周期:{s['date'].min()} ~ {s['date'].max()}")
print(f"总营收:{total_revenue:,.0f}")
print(f"总利润:{total_profit:,.0f} | 利润率:{profit_margin:.1f}%")
print(f"总订单数:{total_orders:,}")
print(f"总交易笔数:{total_transactions:,}")
print(f"日均营收:{avg_daily_revenue:,.0f}")
print(f"平均客单价:{avg_order_value:,.0f}")
print(f"期末现金余额:{latest_cash:,.0f}")
print(f"期末客户总数:{latest_customers:,}")
步骤2:趋势分析(月度)
按月份聚合销售额、利润、订单量,打印月度表:
s = pd.read_csv("sales_detail.csv")
s["month"] = s["date"].str[:7]
monthly = s.groupby("month").agg(营收=("amount","sum"),利润=("profit","sum"),订单量=("quantity","sum"),交易笔数=("date","count")).round(0)
monthly["利润率"] = (monthly["利润"]/monthly["营收"]*100).round(1)
print(monthly.to_string())
pct = monthly["营收"].pct_change() * 100
for m,v in pct.items():
if pd.notna(v):
print(f"{m} 营收环比:{v:+.1f}%")
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.
- 12d ago First seen · 95 lines · 35 tokens per session scan A 511417159e85
business-overview is a skill published in the GitHub repository zj-unicom-ai/UniEmployee (93 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 1,104 once invoked, about $0.0002 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
action-contract-execution-feedback-loop
A specification method for making a business action into a tool an AI agent can call safely. It defines the action’s inputs, outputs, permissions, preconditions, expected effects, error handling, and audit information.
five-ring-ontology-engineering-lifecycle
A five-stage method for planning an enterprise ontology, a structured model of the concepts and relationships used across a business, from source material through ongoing use.
ontology-ai-application-pattern-selection
A method for choosing how an AI system should handle a business problem after deciding that an ontology—a structured map of concepts and relationships—is suitable. It compares patterns such as workflow automation, decision support, knowledge answering, collaboration, and continuous planning.
ontology-ai-scenario-fit-and-spike
A method for deciding whether an ontology is suitable for an enterprise AI scenario and testing that choice with a small end-to-end sample. An ontology is a structured model of concepts, rules, and relationships.
ontology-constraint-and-knowledge-injection
A method for deciding how an ontology’s knowledge should reach an AI model: directly in its instructions, through RAG, or through fine-tuning. RAG retrieves relevant information at answer time; fine-tuning changes the model using training examples.
ontology-golden-case-testing
A testing method for an ontology, which is a structured model of business concepts and rules. It starts with real business questions and expected answers, then adds boundary, missing-data, conflict, permission, and regression tests.