agentmods.dev

y-init

y-init is a command for coding agents from yashs33244/the_y_coding_standard. It costs 85 tokens per session (1,480 once invoked), scanned C, original, MIT.

A setup command that scaffolds an agentic engineering structure in a repository, including instruction files, configuration folders, documentation folders, and starter settings.

In plain words
What is it for?
Use it to initialize a new or existing repository for agent-assisted development, with safeguards against overwriting existing files.
Why use it?
It creates the expected project layout while checking the repository type, technology stack, and existing files first.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the the-y-coding-standard plugin — 1 skill, 10 commands shipped together

not rated 2 2mo ago C scan 85 tokens original MIT
View the source file yashs33244/the_y_coding_standard
Install

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.

agentmods
npx agentmods add commands/yashs33244/the_y_coding_standard/y-init
Clone the repo
git clone --depth 1 https://github.com/yashs33244/the_y_coding_standard

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.

agentmods badge for y-init

README.md
[![agentmods](https://agentmods.dev/badge/commands/yashs33244/the_y_coding_standard/y-init.svg)](https://agentmods.dev/commands/yashs33244/the_y_coding_standard/y-init)
Your own site
<a href="https://agentmods.dev/commands/yashs33244/the_y_coding_standard/y-init"><img src="https://agentmods.dev/badge/commands/yashs33244/the_y_coding_standard/y-init.svg" alt="Measured on agentmods" height="20"></a>
Per session 85 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,480 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00085 $0.01480
Opus 5 $0.00043 $0.00740
Sonnet 5 $0.00017 $0.00296
Haiku 4.5 $0.00009 $0.00148

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

Security

Grade C, and why

y-init scanned grade C 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 4d 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 deletehighDestructive command

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

"Bash(rm -rf:*)",
commands/y-init.md · 142 lines

How it starts

The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/y-init

You are scaffolding the_y_coding_standard agentic engineering stack into the current working directory.

Pre-flight

  1. Run pwd and confirm the working directory with the user via a single concise sentence. Format: "Scaffolding into: . Confirm?". If they decline, stop.
  2. Check if the directory is a git repo. If not, ask whether to git init.
  3. Check for existing files. If AGENTS.md, CLAUDE.md, or any target dotfolder already exists, list them and ask whether to (a) skip those and continue or (b) abort. Never overwrite without consent.

Detect Stack

Detect what's in the repo:

  • package.json -> Node project (check for next, react, vue in dependencies).
  • pyproject.toml / requirements.txt -> Python project.
  • Cargo.toml -> Rust.
  • go.mod -> Go.
  • Empty directory -> greenfield.

Use the detection to inform the AGENTS.md stack section and the .husky pre-commit hook.

Bootstrap Order

Create files in this exact order. Skip any the user said to keep.

  1. README.md if missing: minimal stub with project name, setup, and a pointer to AGENTS.md.
  2. AGENTS.md from the plugin template at ${CLAUDE_PLUGIN_ROOT}/skills/the-y-coding-standard/templates/AGENTS.md. If ${CLAUDE_PLUGIN_ROOT} is unset, fall back to the plugin install path you can detect from the slash command's location. Substitute project name into the TODO markers where you can detect it; leave others.
  3. CLAUDE.md from the plugin template at ${CLAUDE_PLUGIN_ROOT}/skills/the-y-coding-standard/templates/CLAUDE.md.
  4. .gitignore covering: env files, node_modules, pycache, .venv, dist/build, .next, .DS_Store, .vscode/, .idea/, coverage, .claude/settings.local.json, .conductor-worktrees/.
  5. .editorconfig (charset utf-8, lf, indent 2 spaces, 4 for Python).
  6. Folder tree (empty + .gitkeep where needed):
    • .claude/commands/
    • .claude/skills/
    • .claude/hooks/
    • .claude/settings.json (minimal allow/deny set)
    • .claude-plugin/ (empty + .gitkeep, only if user is shipping a plugin)
    • .agents/skills/
    • .conductor/config.json (with sensible defaults)
    • .cursor/rules/01-style.md (pointer to AGENTS.md)
    • .devcontainer/devcontainer.json (matched to detected stack)
    • .devcontainer/Dockerfile (matched to detected stack)
    • .devcontainer/post-create.sh
    • .github/workflows/ci.yml (matched to detected stack)
    • .github/CODEOWNERS (empty placeholder)
    • .github/PULL_REQUEST_TEMPLATE.md
    • .husky/pre-commit (matched to detected stack)
    • .husky/commit-msg (commitlint, only if Node)
    • Docs/architecture.md (stub with one ASCII diagram placeholder)
    • Docs/decisions/.gitkeep
    • Docs/decisions/0001-template.md (ADR template)
    • Docs/runbooks/.gitkeep
    • plans/.gitkeep
    • findings/.gitkeep
    • progress/.gitkeep
    • tests/.gitkeep if no tests directory exists

Read the full file on GitHub · 142 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.

  1. 4d ago First seen · 142 lines · 85 tokens per session scan C bfe672e01d89

Subscribe to this mod's changes

y-init is a command published in the GitHub repository yashs33244/the_y_coding_standard (2 stars, last pushed 2mo ago), licensed MIT. It adds 85 tokens to every session and 1,480 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C 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.

Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

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.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

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.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens