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 ace3000chao/book2startup --skill face-accountability-chartgit clone --depth 1 https://github.com/ace3000chao/book2startupWrote 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/ace3000chao/book2startup/face-accountability-chart)<a href="https://agentmods.dev/skills/ace3000chao/book2startup/face-accountability-chart"><img src="https://agentmods.dev/badge/skills/ace3000chao/book2startup/face-accountability-chart.svg" alt="Measured on agentmods" 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.02383 |
| Opus 5 | $0.00044 | $0.01192 |
| Sonnet 5 | $0.00018 | $0.00477 |
| Haiku 4.5 | $0.00009 | $0.00238 |
Grade A, and why
face-accountability-chart 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 7d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FACe 功能 Accountability Chart
R — 原文 (Reading)
"The FACe tool provides a list of seats (functions) that all organizations must fill. You want to delegate these functions to people who fit your culture and pass two tests: 1. They don't need to be managed. 2. They regularly wow the team with their insights and output."
— Verne Harnish, Scaling Up, 第3章
I — 方法论骨架 (Interpretation)
FACe（Function Accountability Chart，功能问责表）解决的是"对的人在对的位置上"的问题。
核心逻辑： Scaling Up的障碍之一是"瓶颈永远在瓶口"——组织顶层的功能如果没有合适的人来填，所有决策都堵在那里。FACe用一页纸列出企业必须填补的职能座位，并为每个座位指派KPIs和结果指标。
FACe的三个组成部分：
- Seats（功能座位） — 企业必须填补的职能清单，包括：战略/创新、销售/市场、产品/服务、运营/交付、客户成功、财务/合规、人力/文化、技术/IT等
- KPIs（关键绩效指标） — 每个功能每天/每周需要追踪的量化指标，让负责人知道自己是否在轨道上
- Results/Outcomes（结果/成果） — 最终需要交付的财务或运营结果（如：Revenue/Gross Margin/Net Profit/Cash等）
两个测试决定谁坐在哪个座位：
- 测试1：他们不需要被管理（自我驱动）
- 测试2：他们经常用洞察和产出让团队惊叹
与组织架构图的区别： 组织架构图告诉你谁向谁汇报（层级）。FACe告诉你谁对什么结果负责（问责）。层级和问责可以不同——矩阵组织中尤其明显。
典型信号：
- "这事我不知道该找谁"
- "我们有重叠的职责"
- "他明明是VP但产出不够"
- "为什么我们总是错过截止日期"
A1 — 书中的应用 (Past Application)
案例1: Infusionsoft的FACe实践
- 问题: Clate Mask需要在快速扩张中保持组织清晰度
- 方法论的使用: 用FACe明确每个高管负责的结果（Revenue/Gross Margin/Cash），而不是头衔
- 结论: 每次会议都对照FACe讨论进展，确保没有遗漏
- 结果: 年度增长53%，获得5400万投资
案例2: 50人坎的FACe设计
- 问题: 企业从50人向100人扩张时，职能部门开始出现重叠和真空
- 方法论的使用: 在这个阶段，CEO需要坐下来画FACe，明确每个VP负责什么结果
- 结论: 矩阵组织中，职能负责人和业务单元负责人之间必须有清晰分工
- 结果: 避免"谁都管但谁都不负责"的状态
案例3: Dell招Shock Absorber
- 问题: Michael Dell在50人时意识到自己成为公司天花板
- 方法论的使用: 招了专门的HR负责人Barbara Kreisman作为他和组织之间的"缓冲器"
- 结论: 创始人需要把自己的职能也列在FACe上，然后找人来填
- 结果: Dell将公司从创始人依赖型变成组织驱动型，最终Scaling到40,000人
A2 — 触发场景 (Future Trigger) ★
用户会在什么情境下需要这个skill？
- 企业在30-50人时出现"谁负责什么"的混乱 — 业务扩张但架构没跟上，经常出现职责真空或重叠
- 招聘新高管时不知道该设什么KPI — 新VP进来后给什么指标衡量他？
- 高管会议变成"汇报表演"而非决策会议 — 因为没有清晰的问责，每个人只说自己想说的
- 团队出现"瓶颈在顶部"的症状 — 所有审批都到CEO那里，CEO成为决策堵点
- 并购或扩张后组织需要重新对齐 — 买了新公司，但不知道如何整合进现有组织
语言信号（用户的话里出现这些就应激活）
- "这事到底该谁负责"
- "我们有太多重叠的职能"
- "他需要被管着才动"
- "VP进来不知道该做什么"
- "我们需要一个组织架构调整"
- "为什么每次都卡在这里"
- "谁是Revenue的负责人"
- "这个KPI该归谁管"
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.
- 7d ago First seen · 167 lines · 89 tokens per session scan A 7fafae850f72
face-accountability-chart is a skill published in the GitHub repository ace3000chao/book2startup (79 stars, last pushed 4mo ago), licensed MIT. It adds 89 tokens to every session and 2,383 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
teaching-and-leading
Guides founders in leading through modelling behaviour, coaching (not managing), leveraging mirror neurons for mood contagion, distributing leadership titles generously, and using gratitude as a pre-meeting performance enhancer. Covers showing rather than telling, strengths-based leadership, the coach-and-student…
delegation-and-empowerment
Develops the daily practice of effective delegation, accountability diagnosis, and team empowerment. Covers assessing which tasks require personal attention, clarifying scope and context for delegated work, allowing productive struggle, recognising and correcting micromanagement, and leading through influence rather…
inclusive-leadership
Provides daily practices for building genuinely inclusive teams through language audits, bias interruption, equitable hiring, cross-cultural sensitivity, and systemic fairness. Use when team composition lacks diversity, when DEI initiatives face backlash, when women or underrepresented groups stall in advancement…
team-culture-and-dynamics
Provides daily practices for reading team energy, shaping culture deliberately, writing unwritten rules, diagnosing accountability gaps, balancing personality types, and building high-performing teams through social connection. Use when a team feels stuck or stale, when collaboration derails despite good intentions…
apply-extreme-ownership
Use when leading a team and outcomes are falling short — to apply the principle that the leader owns every result, including failures caused by team members, as the non-negotiable foundation for improving performance and building trust.
apply-merit-selection
Use when making any talent selection, promotion, or recommendation decision — to test your evaluation against the reversed-relationship check, because evaluator relationship bias systematically corrupts talent decisions even in well-intentioned evaluators, and merit discipline must be applied at the moment of…