Borrowing it
Nothing to install: this file belongs to yash-gadodia/claude-init. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yash-gadodia/claude-init/main/.claude/skills/update/SKILL.mdgit clone --depth 1 https://github.com/yash-gadodia/claude-initWrote 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/yash-gadodia/claude-init/update)<a href="https://agentmods.dev/skills/yash-gadodia/claude-init/update"><img src="https://agentmods.dev/badge/skills/yash-gadodia/claude-init/update.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.1 | $0.00048 | $0.01685 |
| Opus 5 | $0.00024 | $0.00843 |
| Sonnet 5 | $0.00010 | $0.00337 |
| Haiku 4.5 | $0.00005 | $0.00169 |
Grade A, and why
update 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 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.
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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update: Refresh AI-Native Config
Re-analyze the codebase and update the existing .claude/ configuration to match the current state.
Process
Step 1: Snapshot Current Config
Read and fingerprint every existing config file:
CLAUDE.md— extract sections, note any<!-- custom -->or<!-- generated -->markersARCHITECTURE.md— check if it exists and capture its Directory Structure section for drift comparisonagents/— list all agents and their model/tool configskills/— list all skills and theirpaths:scopes (not just rules — skills can be path-scoped too)rules/— list all rules and theirpaths:scopessettings.json— read hooks, permissions, and anyoutputStylefieldoutput-styles/— list any custom output styles (generatedtdd.md, user-added ones)settings.local.json.example— check it exists so new contributors can bootstrap personal overrides
Step 2: Re-Analyze the Codebase
Run the same analysis as /claude-init (parallel subagents):
- Stack detection (languages, framework, package manager, monorepo)
- Architecture (DB, auth, API, state management)
- Testing & CI (test framework, runner, CI/CD)
- Conventions (commit style, linting, directory structure)
Step 2.5: Template Sync (catch stale generated config)
Codebase drift is not the only reason config goes stale — the templates themselves improve over time, and a project generated by an older claude-init keeps the old (sometimes buggy) output. /update must close that gap, because nothing auto-propagates: generated .claude/ files are static copies with no live link back to the templates.
Resolve the current templates the same way /claude-init does — first match wins:
${CLAUDE_SKILL_DIR}/../../../templates/(running from a cloned repo)~/.claude/claude-init-templates/(global install)
If neither exists, skip this step (note it in the report so the user knows template-sync was unavailable) and continue with the codebase-drift diff.
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 · 128 lines · 48 tokens per session scan A 8151e84d3803
update is a skill published in the GitHub repository yash-gadodia/claude-init (5 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 1,685 once invoked, about $0.0002 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
code-review
You are a senior code reviewer. You receive diffs via stdin.
mainframe
Use when Pi writes, reviews, or executes bash; use MAINFRAME tools, AWM, and guarded function execution when available.
mainframe
Discover MAINFRAME read-only shell helpers and route durable agent authority through its control plane when available.
skit
Run, inspect, and manage entries in the user's skit library — their personal hub, manager, and launcher for scripts in many languages (Python, shell, JS/TS, and more), executables, command templates, and AI-agent prompts, with typed parameter forms, saved presets, and per-entry launch policy. Use when the user asks to…
setup
Use when setting up a project, adding linting, formatting, git hooks, or type checking. Detects the language and installs that ecosystem's lint/format/hooks toolchain (JS/TS, Python, Go, Rust).
deps
Use when hardening a dependency supply chain, pinning versions, adding registry/security flags, or setting up Renovate. Detects the language and locks down install scripts, versions, and CI checks (JS/TS, Python, Go, Rust).