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 vivy-yi/finance-skills --skill board-meeting-managementgit clone --depth 1 https://github.com/vivy-yi/finance-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/skills/vivy-yi/finance-skills/board-meeting-management)<a href="https://agentmods.dev/skills/vivy-yi/finance-skills/board-meeting-management"><img src="https://agentmods.dev/badge/skills/vivy-yi/finance-skills/board-meeting-management/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/vivy-yi/finance-skills/board-meeting-management"><img src="https://agentmods.dev/badge/skills/vivy-yi/finance-skills/board-meeting-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00089 | $0.02005 |
| Opus 5 | $0.00044 | $0.01002 |
| Sonnet 5 | $0.00018 | $0.00401 |
| Haiku 4.5 | $0.00009 | $0.00200 |
Grade A, and why
board-meeting-management 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
加载上下文
首次使用时: 读取 ../../CLAUDE.md 获取场景级配置(董事会职责/议事规则/委员名单)。
/board-meeting-management — 董事会会议管理
Examples
→ 示例:用户说"年度董事会计划要更新,需要财务团队支持哪些议题",系统应调用本技能,按年度公司治理要求规划董事会议题。
→ 示例:用户说"有个董事临时要加一个紧急议题进下周董事会,需要通知所有相关方",系统应调用本技能,生成临时议题处理流程。
→ 示例:用户说"董事会决议有一项授权 CFO 处置资产,需要起草决议文",系统应调用本技能,生成董事会决议草案。
第一步:确认会议基本信息
会议基本信息:
□ 会议类型:[董事会/审计委员会/战略委员会/薪酬委员会]
□ 会议日期:[YYYY-MM-DD]
□ 会议时间:[HH:MM]-[HH:MM]
□ 会议地点:[线上/线下地址]
□ 会议时长:[X] 小时
□ 主持人:[姓名]
参会人员:
□ 董事:[X] 人
→ 执行董事:[姓名1]、[姓名2]
→ 非执行董事:[姓名3]、[姓名4]
→ 独立董事:[姓名5](符合 [X]% 要求)
□ 列席人员:[姓名]([职位])、[姓名]([职位])
□ 秘书:[姓名] — [公司] 董事会秘书
□ 外部顾问(如适用):[姓名]([机构])
第二步:议程设计
标准议程框架:
□ 董事会标准议程:
1. 会议召集确认(法定人数)
2. 利益冲突声明
3. 上次会议纪要确认
4. 报告事项
- 经营报告
- 财务报告
- 战略执行报告
5. 决议事项
6. 讨论事项
7. 其他事项
8. 下次会议安排
本次会议具体议程:
□ 决议事项(如有):
1. [事项] — 须普通决议 / 特别决议
2. [事项] — 须普通决议 / 特别决议
□ 报告事项:
1. [报告1]
2. [报告2]
□ 讨论事项(如有):
1. [讨论议题]
□ 闭门讨论事项(如仅独立董事):
1. [议题]
第三步:材料完整性管理
材料准备清单:
□ 会议通知:[✅ 已发送 / ⚠️ 待发送] — 发送日期 [YYYY-MM-DD]
□ 议程:[✅ 已确认 / ⚠️ 待确认]
□ 上次会议纪要:[✅ 已准备 / ⚠️ 待准备]
□ 决议事项材料:
→ [事项1] — 材料 [✅ 已准备 / ⚠️ 缺失] — 准备人 [姓名]
→ [事项2] — 材料 [✅ 已准备 / ⚠️ 缺失] — 准备人 [姓名]
□ 报告事项材料:
→ 经营报告 [✅ 已准备 / ⚠️ 缺失]
→ 财务报告 [✅ 已准备 / ⚠️ 缺失]
材料审核状态:
□ 材料完整性检查:[✅ 完整 / 🔴 缺失 X 份]
□ 保密信息检查:[✅ 已脱敏 / ⚠️ 需处理]
□ 法律合规检查:[✅ 通过 / ⚠️ 需法务确认]
□ 财务数据准确性:[✅ 已核实 / ⚠️ 待核实]
第四步:会议记录准备
会议记录模板(提前准备):
□ 记录格式:[标准模板]
□ 记录人:[姓名]
□ 录音设备:[是/否 — 须提前告知董事]
□ 须记录内容:
→ 参会人员出勤情况
→ 每个议题的讨论要点
→ 董事提出的主要问题和意见
→ 形成的决议或决定
→ 须采取的行动项(Action Items)
→ 下次会议时间
Action Items 模板:
□ 行动项记录格式:
| # | 行动项 | 负责人 | 完成日期 | 状态 |
|---|--------|--------|---------|------|
| 1 | [事项] | [姓名] | [日期] | [待确认/进行中/已完成] |
第五步:会前跟进
参会确认:
□ 董事参会确认:[X]/[X] 人已确认
□ 确认缺席:[姓名] — 委托 [姓名] 代理表决
□ 未确认董事:[姓名] — 跟进 [联系方式]
□ 法定人数:[✅ 满足 / 🔴 不足]
材料分发:
□ 材料发送日期:[YYYY-MM-DD](会议前 [X] 天)
□ 分发方式:[加密邮件/专人送达]
□ 材料保密级别:[机密/绝密]
□ 确认签收:[X]/[X] 位董事已签收
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 · 226 lines · 89 tokens per session scan A 8c15732ccb5e
board-meeting-management is a skill published in the GitHub repository vivy-yi/finance-skills (29 stars, last pushed 3mo ago), licensed MIT. It adds 89 tokens to every session and 2,005 once invoked, about $0.0004 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
hive.colony-progress-tracker
Claim tasks, record step progress, and verify SOP gates in the colony SQLite queue. Applies when your spawn message includes a dbpath field.
prd
A guide for writing a PRD, or Product Requirements Document, which explains what a product or feature should achieve and who it is for. It covers goals, users, success measures, limits, prior work, and excluded scope.
product-discovery
Product discovery workflow with OST, assumption testing, and interview scripts.
planning
A guide for planning software features and turning requests into clear requirements. It uses EARS, a plain format for stating what a system must do under specific conditions.
auto-status
A project dashboard skill that reports the current specification status for a project and its submodules. A specification is a written description of what should be built and how it should behave.
github-digest
You are a GitHub assistant generating a daily PR + issues digest for the user.