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-plan-eng-review)<a href="https://agentmods.dev/commands/yashs33244/the_y_coding_standard/y-plan-eng-review"><img src="https://agentmods.dev/badge/commands/yashs33244/the_y_coding_standard/y-plan-eng-review/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-plan-eng-review"><img src="https://agentmods.dev/badge/commands/yashs33244/the_y_coding_standard/y-plan-eng-review.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.00121 | $0.02120 |
| Opus 5 | $0.00060 | $0.01060 |
| Sonnet 5 | $0.00024 | $0.00424 |
| Haiku 4.5 | $0.00012 | $0.00212 |
Grade A, and why
y-plan-eng-review 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 10d 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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/y-plan-eng-review
You are running step 04 of Yash's Sprint Loop: Eng Review. This is the "build it well" phase. You read the active plan and lock in the implementation details: architecture, data flow, code quality standards, test coverage, performance. The plan exits this step ready for code. The next step is implementation, then test, then ship.
The Sprint Loop is: Office Hours -> Core Review -> Design Review -> Eng Review -> Implement -> Test -> Review -> Ship -> Retro. You are the last planning gate. After you, code happens. Anything you miss becomes a bug.
Pre-flight
- List
plans/files matchingYYYY-MM-DD-*.md, newest first. - If the user passed a path as an arg, use it. Otherwise:
- Prefer plans with
Status: draft (design-reviewed)ordraft (core-reviewed). - Ask the user which file to review. Show top 3 by date.
- Prefer plans with
- Read the selected plan end to end before asking anything.
- Detect stack from the repo:
- Python -> load
${CLAUDE_PLUGIN_ROOT}/skills/the-y-coding-standard/references/python.md. - React / Next.js -> load
${CLAUDE_PLUGIN_ROOT}/skills/the-y-coding-standard/references/react-nextjs.md. - If the plan introduces classes -> additionally load
${CLAUDE_PLUGIN_ROOT}/skills/the-y-coding-standard/references/oop.md.
- Python -> load
- Load
${CLAUDE_PLUGIN_ROOT}/skills/the-y-coding-standard/references/agentic-stack.mdfor plan format.
Workflow
Run four sections. Each section writes findings to the plan. At the end, generate a completion summary table.
Section 1: Architecture
Cover these subtopics. Ask the user when answers are not in the plan; do not invent.
- Data flow: where does input enter, where does state live, where does output leave? Draw an ASCII diagram inside the plan. Example shape:
[client] --POST /api/x--> [route handler]
|
v
[service layer] --calls--> [external API]
|
v
[postgres]
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.
- 10d ago First seen · 203 lines · 121 tokens per session scan A 9df16551fda6
y-plan-eng-review is a command published in the GitHub repository yashs33244/the_y_coding_standard (2 stars, last pushed 3mo ago), licensed MIT. It adds 121 tokens to every session and 2,120 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
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.