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 agentmods add skills/code-saurabh/openskills/office-hoursnpx skills add CODE-SAURABH/OpenSkills --skill office-hoursgit clone --depth 1 https://github.com/CODE-SAURABH/OpenSkillsWrote 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/code-saurabh/openskills/office-hours)<a href="https://agentmods.dev/skills/code-saurabh/openskills/office-hours"><img src="https://agentmods.dev/badge/skills/code-saurabh/openskills/office-hours.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 | $0.00056 | $0.04344 |
| Opus 5 | $0.00028 | $0.02172 |
| Sonnet 5 | $0.00011 | $0.00869 |
| Haiku 4.5 | $0.00006 | $0.00434 |
Grade A, and why
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 3d 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 — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Office Hours — Pre-Code Ideation & Idea Validation
Run this skill before any code is written. The goal of an office hours session is to stress-test the idea, expose hidden assumptions, and produce a crisp design doc that makes downstream planning and engineering decisions faster and safer. Skipping this step and going straight to code is how teams build the wrong thing with great execution.
Office hours is not brainstorming for its own sake. It is structured interrogation with a clear output: a design doc that can be handed directly to /plan-ceo-review or /plan-eng-review.
When to Invoke This Skill
Proactively invoke this skill — do not answer directly — when:
- The user describes a new product idea, feature concept, or startup direction
- The user asks "is this worth building?", "should I build this?", or "help me think through this"
- The user is exploring a concept before any code exists
- The user says "brainstorm this" or "office hours"
- The user is about to spec or plan something with unvalidated demand assumptions
Always run office hours before:
/plan-ceo-review(strategy scope)/plan-eng-review(architecture decisions)- Generating a project spec or writing the first line of code
Two Modes
Detect which mode applies based on context. Ask if unclear.
Mode 1: Startup Mode
Triggers: B2B or B2C product, SaaS, marketplace, consumer app intended to find customers and generate revenue.
Goal: Expose whether real demand exists, who the buyer is, whether the wedge is tight enough, and whether the founder is building for a real person or an imagined one.
Posture: Act as a YC partner running a 10-minute office hours session. Be direct, be skeptical of assertions, demand specificity. Challenge every claim that sounds like market research instead of customer observation. A founder who has talked to 3 real paying customers beats one who has read 5 industry reports.
Mode 2: Builder Mode
Triggers: Side project, open-source tool, hackathon build, learning project, personal automation, indie product.
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.
- 3d ago First seen · 375 lines · 56 tokens per session scan A ab396e232f21
office-hours is a skill published in the GitHub repository CODE-SAURABH/OpenSkills (2 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 4,344 once invoked, about $0.0003 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-31.
Other skills, from other repositories
ecommerce-landing-page
Audit and optimize e-commerce landing pages for conversion. CTA placement, trust signals, page structure, copy optimization, and A/B testing strategy for product pages, collection pages, and campaign landing pages.
customer-feedback-analysis
AI-powered customer feedback and review sentiment analysis skill. Extracts pain points, feature requests, and improvement priorities from customer reviews across e-commerce platforms.
ads-launch
Draft or explicitly apply a paid-ad campaign launch through Claude Ads capability-gated adapters. Use for campaign creation, launch plans, publishing ads, activating campaigns, uploading creative, or requests to push a campaign live.
api-response-optimization
Optimizes API performance through payload reduction, caching strategies, and compression techniques. Use when improving API response times, reducing bandwidth usage, or implementing efficient caching.
ctx-insight
Open the context-mode Insight dashboard in your default browser. Insight is the hosted analytics layer for AI-assisted engineering teams — per-engineer productive rate, retry waste, blocker detection, role-narrowed views. Trigger: /context-mode:ctx-insight.
debugging
Systematically diagnose and fix software bugs by analyzing error messages, stack traces, logs, and runtime behavior across multiple languages. Use when the user requests debugging or provides relevant inputs for this workflow.