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 annual-audit-planninggit 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/annual-audit-planning)<a href="https://agentmods.dev/skills/vivy-yi/finance-skills/annual-audit-planning"><img src="https://agentmods.dev/badge/skills/vivy-yi/finance-skills/annual-audit-planning/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/annual-audit-planning"><img src="https://agentmods.dev/badge/skills/vivy-yi/finance-skills/annual-audit-planning.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.00080 | $0.01300 |
| Opus 5 | $0.00040 | $0.00650 |
| Sonnet 5 | $0.00016 | $0.00260 |
| Haiku 4.5 | $0.00008 | $0.00130 |
Grade A, and why
annual-audit-planning 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 9d 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
加载上下文
首次使用时: 读取 ../../CLAUDE.md 获取审计范围/高风险领域定义/审计标准。
/annual-audit-planning — 年度审计计划制定
第一步:风险评估与优先级排序
□ 收集风险信息:
□ 上年度审计发现分布
□ 重大风险事件(舞弊/投诉/监管处罚)
□ 业务/组织变化(扩张/并购/系统上线)
□ 行业风险趋势
□ 风险评分(可能性 × 影响):
□ 🔴 高风险:可能性 [高/中] × 影响 [高/中] → 优先审计
□ ⚠️ 中风险:可能性 [中/低] × 影响 [中/高] → 常规审计
□ ✅ 低风险:可能性 [低] × 影响 [低/中] → 可延后或合并
□ 高风险领域清单(来自 CLAUDE.md):
□ 🔴 现金/银行存款管理
□ 🔴 采购与付款循环
□ 🔴 收入与收款循环
□ 🔴 关联交易
□ 🔴 舞弊高发岗位
□ ⚠️ 存货管理
□ ⚠️ 固定资产管理
□ ⚠️ 税务合规
第二步:确定审计范围
□ 被审计单位/流程清单:
□ 全资子公司:[X] 家 → 选择 [X] 家
□ 控股子公司:[X] 家 → 选择 [X] 家
□ 分支机构/事业部:[X] 个 → 选择 [X] 个
□ 总部职能部门:[X] 个 → 选择 [X] 个
□ 专项流程审计:[X] 个
□ 审计类型分布:
□ 全面审计(覆盖多个流程):[X] 项
□ 专项审计(单一流程深挖):[X] 项
□ 持续审计(高风险流程实时监控):[X] 项
第三步:资源配置
□ 可用审计资源:
□ 审计人员:[X] 人
□ 可用人天:[X] 人天(每年)
□ 资源配置:
□ 高风险领域(每个 [X] 人天):[X] 人天
□ 中风险领域(每个 [X] 人天):[X] 人天
□ 低风险领域(每个 [X] 人天):[X] 人天
□ 管理/报告/整改跟踪:[X] 人天
□ 总需求:[X] 人天 vs 可用 [X] 人天
□ 是否需要外包/外部专家:[是/否]
□ 外包内容:[...]
第四步:编制年度审计计划
□ 年度审计日历:
□ Q1:[审计项 1/2] — 负责人 [X]
□ Q2:[审计项 3/4] — 负责人 [X]
□ Q3:[审计项 5/6] — 负责人 [X]
□ Q4:[年度审计总结 + 下年计划制定]
□ 重大审计里程碑:
□ Q1 末:完成上年度整改验证报告
□ Q2 末:中期审计报告
□ Q3 末:专项审计报告
□ Q4 末:年度审计总结 + 下年计划初稿
输出格式
═══════════════════════════════════════
[YYYY] 年度内部审计计划
编制人:[审计总监]
审核人:[审计委员会主席]
批准日期:[YYYY-MM-DD]
═══════════════════════════════════════
【一、风险评估结果】
□ 高风险领域(须优先覆盖):
□ [领域 1] — 风险评分 [高] — 建议审计时间 [Q1/Q2]
□ [领域 2] — 风险评分 [高] — 建议审计时间 [Q1/Q2]
□ 中风险领域(常规覆盖):
□ [领域 3] — 风险评分 [中]
□ 低风险领域(选择性覆盖):
□ [领域 4] — 风险评分 [低]
【二、审计范围】
□ 全年计划审计:[X] 个单位/流程
□ 全面审计:[X] 项
□ 专项审计:[X] 项
□ 持续审计:[X] 项
【三、资源需求】
□ 人天需求:[X] 人天
□ 可用资源:[X] 人天
□ 缺口:[X] 人天 → 解决方案 [描述]
【四、审计日历】
| 季度 | 审计项目 | 负责人 | 预计天数 | 备注 |
|------|----------|--------|----------|------|
| Q1 | [项目1] | [姓名] | [X] | |
| Q2 | [项目2] | [姓名] | [X] | |
| ... | ... | ... | ... | |
【五、须审计委员会关注事项】
□ [事项 1]
□ [事项 2]
═══════════════════════════════════════
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.
- 9d ago First seen · 154 lines · 80 tokens per session scan A 6e70b5ffdd5a
annual-audit-planning is a skill published in the GitHub repository vivy-yi/finance-skills (29 stars, last pushed 3mo ago), licensed MIT. It adds 80 tokens to every session and 1,300 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-09-03.
Other skills, from other repositories
infographics
Create professional infographics using Nano Banana Pro AI with smart iterative refinement. Uses Gemini 3 Pro for quality review. Integrates research-lookup and web search for accurate data. Supports 10 infographic types, 8 industry styles, and colorblind-safe palettes.
similarity-search-patterns
Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.
figma-implement-design
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a…
datavis
Comprehensive data visualization toolkit for creating beautiful, mathematically elegant visualizations with D3.js, Chart.js, and custom SVG. Use when (1) building interactive data visualizations, (2) designing color palettes for charts, (3) choosing scales and visual encodings, (4) creating data pipelines from…
spec-kit-vibe-compat
Compatibility router for /speckit. workflows into /vibe-first Codex execution.
detecting-data-anomalies
Investigate outliers, rare events, spikes, and suspicious records in datasets. Use as an explicit anomaly-analysis helper when you want concrete anomaly-detection workflow guidance, not generic data validation or end-to-end ML ownership.