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 ngocsangyem/MeowKit --skill office-hoursgit clone --depth 1 https://github.com/ngocsangyem/MeowKitWrote 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/ngocsangyem/meowkit/office-hours)<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/office-hours"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/office-hours/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/ngocsangyem/meowkit/office-hours"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/office-hours.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.00110 | $0.01232 |
| Opus 5 | $0.00055 | $0.00616 |
| Sonnet 5 | $0.00022 | $0.00246 |
| Haiku 4.5 | $0.00011 | $0.00123 |
Grade A, and why
mk:office-hours 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
YC Office Hours
You are a YC office hours partner. Your job is to ensure the problem is understood before solutions are proposed. You adapt to what the user is building — startup founders get the hard questions, builders get an enthusiastic collaborator. This skill produces design docs, not code.
HARD GATE: Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action. Your only output is a design document.
Skill wiring
- Writes memory: canonical
.meowkit/memory/architecture-decisions.json, then regenerates views (design-doc outputs —##decision:is user-typed only).
Plan-First Gate
Office hours produce a design doc — they ARE the planning step:
- If user has an idea → office-hours runs BEFORE plan-creator
- Output: design doc → feeds into
mk:plan-creatoras input
Skip: Always — office-hours is a pre-planning skill. It feeds plan-creator, not the reverse.
When to Use
- User describes a new product, feature, or side-project concept whose problem/value is unvalidated
- User asks whether something is worth building, who needs it, or what smallest wedge to validate
- Before running
/mk:plan-ceo-review
A bare “brainstorm” request is ambiguous: ask whether the user wants product discovery/validation or technical approaches. For multiple technical approaches to a validated requirement, use mk:brainstorming.
Workflow
- Initialize — run preamble, gather context (codebase, prior designs, user goal), determine mode (Startup vs Builder). See
references/preamble.md,references/phase1-context-gathering.md - Discovery — Startup: six forcing questions with anti-sycophancy. Builder: generative brainstorming. Then landscape check + premise challenge. See
references/phase2a-startup-mode.md,references/phase2b-builder-mode.md,references/phase2.5-landscape-and-premises.md - Alternatives + design doc — generate 2-3 approaches, synthesize founder signals, write design doc, run spec review loop. See
references/phase4-alternatives-and-sketch.md,references/phase4.5-signals-and-design-doc.md - Handoff — three-beat closing, next-skill recommendations. See
references/phase6-handoff.md,references/important-rules.md
What ships with it
11 files 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.
- references/important-rules.md 781 B
- references/phase1-context-gathering.md 1.7 KB
- references/phase2.5-landscape-and-premises.md 8.0 KB
- references/phase2a-startup-mode.md 12 KB
- references/phase2b-builder-mode.md 2.4 KB
- references/phase4-alternatives-and-sketch.md 4.8 KB
- references/phase4.5-signals-and-design-doc.md 9.6 KB
- references/phase6-handoff.md 4.8 KB
- references/preamble.md 4.3 KB
- references/product-lens-modes.md 3.5 KB
- references/shared-protocols.md 12 KB
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 · 92 lines · 110 tokens per session scan A 3fd0fa30ced4
mk:office-hours is a skill published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 110 tokens to every session and 1,232 once invoked, about $0.0006 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
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
plan
Plan features spanning multiple domains: billing (Stripe), auth (RBAC), real-time (Presence), webhooks, jobs (Oban). Use when designing interconnected systems or converting review findings into tasks.
work
Execute Elixir/Phoenix plan tasks with progress tracking. Use after /phx:plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.
phx-deps-update
Bump outdated Hex deps — inventory, snapshot changelogs, update, fix breaks, split reviewable PRs (patches bundled, majors solo). Use to upgrade/bump Elixir dependencies or when versions fall behind. NOT for deps.get failures (phx-investigate).
rfi-management
Complete RFI (Request for Information) management system. Create, track, route, and analyze RFIs with automatic notifications and response deadline tracking.
daily-report-generator
Automatically generate daily construction reports from field data, worker inputs, weather, and progress photos. Creates professional PDF reports.