A repository governance audit command that checks security, policies, auditability, compliance, and permissions before a release. It uses three parallel reviewers and saves their combined findings as a dated Markdown file.

Run it in a Git repository before releasing code, with an optional quick mode that skips the slower dependency scan.

It gathers release checks and findings in one repeatable report instead of leaving governance review scattered across manual checks.

y-govern — Command for Claude Code by yashs33244

Install

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.

Claude Code

/plugin marketplace add yashs33244/the_y_coding_standard

Claude Code

/plugin install the-y-coding-standard

Made for: Claude Code.

Or install the-y-coding-standard, the plugin that ships this one along with the rest of its 1 skill, 10 commands.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/yashs33244/the_y_coding_standard/y-govern/github.svg)](https://agentmods.dev/commands/yashs33244/the_y_coding_standard/y-govern)

Your own site

<a href="https://agentmods.dev/commands/yashs33244/the_y_coding_standard/y-govern"><img src="https://agentmods.dev/badge/commands/yashs33244/the_y_coding_standard/y-govern/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/yashs33244/the_y_coding_standard/y-govern"><img src="https://agentmods.dev/badge/commands/yashs33244/the_y_coding_standard/y-govern.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 61 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,479 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00061	$0.01479
Opus 5	$0.00030	$0.00740
Sonnet 5	$0.00012	$0.00296
Haiku 4.5	$0.00006	$0.00148

Measured 8d ago against content hash 8afe67b4e738, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade B, and why

y-govern scanned grade B with 1 finding 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 8d 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.

Recursive force deletemediumDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- Are destructive operations (rm -rf, git push --force, sudo) denied?

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

commands/y-govern.md · 161 lines

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-govern

You are running the_y_coding_standard governance audit. Goal: produce a findings file at findings/YYYY-MM-DD-governance.md covering five governance dimensions (security, policy, auditability, compliance, permissions).

Pre-flight

Verify the working directory is a git repo. If not, abort with a helpful message.
Verify the canonical folder structure exists. If findings/ is missing, create it.
Load the governance reference at ${CLAUDE_PLUGIN_ROOT}/skills/the-y-coding-standard/references/governance.md. Use it as the policy catalog.
Identify the plugin install path. Scripts are at ${CLAUDE_PLUGIN_ROOT}/skills/the-y-coding-standard/scripts/.

Parse Args

Accept optional flags:

--quick: skip slow dep scan (audit_deps.py).
--full (default): run everything.

Dispatch Three Sub-Agents in Parallel

Use the Agent tool with subagent_type: general-purpose. Dispatch all three in a single message so they run concurrently.

Sub-agent A: Security

Prompt for the agent (self-contained, since the agent has no shared context):

"You are running the SECURITY portion of the_y_coding_standard governance audit on the repo at .

Tasks:

Run uv run ${CLAUDE_PLUGIN_ROOT}/skills/the-y-coding-standard/scripts/scan_secrets.py <PWD> and capture JSON output.
Grep for common dangerous patterns across the codebase:
- Python: eval(, exec(, pickle.loads, yaml.load( (without safe_load), subprocess(...shell=True, verify=False.
- SQL string interpolation: regex f\"SELECT.*\\{ or \".*\" \\+ .* near sql calls.
- TLS-disabled HTTP: rejectUnauthorized: false (Node), verify=False (Python requests).
Inspect any .env files committed (should be only .env.example).
Check package.json / pyproject.toml for obviously suspicious deps.
Inspect .github/workflows/*.yml for secret exposure (env or secrets used on pull_request_target).

Return a JSON findings list. Severity P0 / P1 / P2 / P3. For each finding: file:line, message, severity, recommended fix.

Read the full file on GitHub · 161 lines

Changes

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.

8d ago First seen · 161 lines · 61 tokens per session scan B 8afe67b4e738

Subscribe to this mod's changes

y-govern is a command published in the GitHub repository yashs33244/the_y_coding_standard (2 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 1,479 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Legal and compliance Security

deps-audit

Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.

wshobson/agents · 23 tokens

review-epo-claims

Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.

RobThePCGuy/Claude-Patent-Creator · 22 tokens

voice-compliance

Voice/telephony compliance check — invokes voice-ai-reviewer to produce TM-voice-{slug}.md with TCPA, STIR/SHAKEN, state recording-consent, EU AI Act Art. 50, and synth-voice deepfake-law gaps.

avelikiy/great_cto · 53 tokens

review-policy

Review a policy document for structure, coverage, and language quality.

mlunato47/claude-grc-plugin · 12 tokens

at-dsgvo

You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…

tractorjuice/arc-kit · 35 tokens

au-pspf

You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.

tractorjuice/arc-kit · 33 tokens

y-govern