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 enterprise-salesgit 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/enterprise-sales)<a href="https://agentmods.dev/skills/zj-unicom-ai/uniemployee/enterprise-sales"><img src="https://agentmods.dev/badge/skills/zj-unicom-ai/uniemployee/enterprise-sales/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/enterprise-sales"><img src="https://agentmods.dev/badge/skills/zj-unicom-ai/uniemployee/enterprise-sales.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.00040 | $0.01064 |
| Opus 5.5 | $0.00016 | $0.00426 |
| Sonnet 5.5 | $0.00008 | $0.00213 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
enterprise-sales 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 1mo 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
政企客户拜访规程
触发条件
- 用户说"拜访客户"、"准备方案"、"出方案"、"生成文档"、"做方案"
- 用户提到政企客户名称（如"张总"、"应急局"、"教育局"等）
- 用户要求生成或导出 Word 文档
- 用户口述拜访情况，要求整理拜访纪要、记录客户反馈
执行步骤（按顺序，不可跳过）
步骤 1：查客户档案
优先调用 kb_search 检索「客户档案」知识库：
- 先查
客户名 + 客户档案 - 再查
客户名 + 历史消费 + 已购产品 - 客户所属企业、行业、职级、拜访记录也在该知识库中检索
若知识库未命中，再调用 CRM 的 customer_profile 查询客户档案；
仍未命中则告知用户补充客户信息。
步骤 2：分析客户行业
根据客户所属行业（如数字政府、应急消防、教育、工业互联网等），判断产品匹配方向：
- 通信需求 → 企业通信云服务（云录音/云转写/云名片等）
- 组网安全需求 → 云安全（组网专线/安全专线）
- 消防应急需求 → AI 视频分析（烟火识别）
- 园区/社区管理需求 → 智慧园区
- AI大模型/智能化需求 → 企业大模型应用平台
- 不确定时调 kb_search 检索产品目录
步骤 3：检索产品方案
调 kb_search 检索该行业相关的产品资料、解决方案和案例：
- 先查
产品名 + 产品介绍 - 再查
行业名 + 行业方案 + 案例 - 最后查
产品名 + 竞品对比
步骤 4：生成方案文档
生成 Word 文档的流程（按顺序执行）：
- 读取脚本文件：先执行
read_file("/skills/enterprise-sales/scripts/gen_solution.js")查看生成脚本的参数格式 - 准备参数：把产品清单组装为 JSON 格式，格式为
[{"name":"产品名","qty":"数量","price":"单价","subtotal":"小计"},...] - 执行生成命令：用
execute运行 node 脚本execute("node backend/skills/enterprise-sales/scripts/gen_solution.js workspace/data/解决方案_客户名.docx "客户名" "企业名" "需求分析" '[{"name":"产品A","qty":"1","price":"100","subtotal":"100"}]' "100.00") - 确认结果：脚本输出"文档已生成：xxx"即表示成功，告知用户文档路径
生成的文档包含：
- 客户名称、企业
- 需求分析
- 推荐产品方案表格（产品名、数量、单价、总价）
- 方案优势
- 售后服务承诺
步骤 5：拜访后纪要
用户口述拜访情况或要求整理拜访记录时（按顺序执行）：
- 结构化整理：把口述内容整理为纪要，固定字段： 拜访时间 / 客户与企业 / 参与人 / 沟通要点 / 客户反馈与顾虑 / 下一步行动（含责任人与时间）
- 落档：用
write_file把纪要写入workspace/data/拜访纪要_客户名_日期.md - 沉淀记忆：提炼客户偏好与关键承诺（如"X1 音箱不喜欢黑色"、"月底要报价"），
用
write_file追加到/memories/AGENTS.md（跨会话记忆） - 升级红线：纪要中出现客户投诉或重大诉求（折扣/赔偿/超标准 SLA）时，
必须调用
create_ticket走人工审批，审批通过前不得向客户承诺处理结果
回答风格
- 先说结论（"已为您生成方案"），再概要说明文档内容
- 涉及产品用正式名称（企业通信云、AI 视频分析等）
- 数据必须来自真实查询结果
- 主动询问是否需要调整方案
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.
- 1mo ago Changed · +14 lines · +6 tokens per session eaaf3ac4f7ed
- 1mo ago First seen · 63 lines · 34 tokens per session scan A b672d74ee046
enterprise-sales is a skill published in the GitHub repository zj-unicom-ai/UniEmployee (615 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 1,064 once invoked, about $0.0002 per session on Opus 5.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.
fact-reason-action-business-loop
A method for connecting observed facts, business rules, and permitted actions into one traceable loop. It records what happened, explains why a conclusion follows, defines allowed actions, and captures the results.
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.