Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yashs33244/the_y_coding_standard/plugin install the-y-coding-standardWrote 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/commands/yashs33244/the_y_coding_standard/y-office-hours)<a href="https://agentmods.dev/commands/yashs33244/the_y_coding_standard/y-office-hours"><img src="https://agentmods.dev/badge/commands/yashs33244/the_y_coding_standard/y-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/commands/yashs33244/the_y_coding_standard/y-office-hours"><img src="https://agentmods.dev/badge/commands/yashs33244/the_y_coding_standard/y-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.00127 | $0.01578 |
| Opus 5 | $0.00063 | $0.00789 |
| Sonnet 5 | $0.00025 | $0.00316 |
| Haiku 4.5 | $0.00013 | $0.00158 |
Grade A, and why
y-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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/y-office-hours
You are running step 01 of Yash's Sprint Loop: Office Hours. This is the "what should we build?" phase. You are NOT writing code. You are NOT writing an engineering plan. You are interrogating an idea before it deserves either. Output is a design doc in plans/ that the next Sprint Loop step (/y-plan-core-review) will scope-lock.
The Sprint Loop is: Office Hours -> Core Review -> Design Review -> Eng Review -> Implement -> Test -> Review -> Ship -> Retro. You are the first gate. Bad ideas die here, cheap. Good ideas get sharpened.
Pre-flight
- Check
plans/exists. If missing, create it with a.gitkeep. - List existing plan files in
plans/. Pattern:YYYY-MM-DD-<slug>.md. - If the user already has an active plan file matching the current branch name or the topic they mention, ask one concise question: "Update existing
plans/<file>.mdor create a new one?". Default to new on ambiguous answers. - If creating new: derive a slug from the idea in 2-4 hyphenated words. Filename:
plans/$(date +%Y-%m-%d)-<slug>.md. - Load the plan template from
${CLAUDE_PLUGIN_ROOT}/skills/the-y-coding-standard/references/agentic-stack.md(the "Plan File Template" section). Adapt sections for an office-hours-stage doc.
Workflow
Run the four probes in order. Do NOT batch all questions in one wall of text. Ask one focused question per probe, wait, then move on. Yash hates question floods.
Probe 1: Problem definition
Ask the user, in order, one at a time:
- "What's the actual problem? Describe it as a sentence a user would say, not as a feature spec."
- "Who specifically hits this problem? Be concrete: 'me', 'devs at my company', 'finance teams using '. Not 'users'."
- "What's the trigger? What event makes someone notice this problem right now?"
If the user describes a solution instead of a problem, push back. Format: "That's a solution. What's the problem the solution would solve?". Do not move on until you have a problem, an owner, and a trigger.
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 · 161 lines · 127 tokens per session scan A ec38b0dd02fa
y-office-hours is a command published in the GitHub repository yashs33244/the_y_coding_standard (2 stars, last pushed 3mo ago), licensed MIT. It adds 127 tokens to every session and 1,578 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.