Borrowing it
Nothing to install: this file belongs to vinhnx/vtchat. 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/vinhnx/vtchat/main/.opencode/commands/codemod.mdgit clone --depth 1 https://github.com/vinhnx/vtchatWrote 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/vinhnx/vtchat/codemod)<a href="https://agentmods.dev/commands/vinhnx/vtchat/codemod"><img src="https://agentmods.dev/badge/commands/vinhnx/vtchat/codemod/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/vinhnx/vtchat/codemod"><img src="https://agentmods.dev/badge/commands/vinhnx/vtchat/codemod.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.00000 | $0.00373 |
| Opus 5.5 | $0.00000 | $0.00149 |
| Sonnet 5.5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
codemod 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 today.
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.
What it actually says
Treat any text passed with /codemod as a codemod task.
Use the installed codemod skill as the source of truth.
First classify intent:
- If the user asks to create, build, scaffold, write, improve, test, or publish a codemod or codemod workspace, treat it as a codemod-authoring request.
- Otherwise, treat it as codemod discovery or execution: search the registry, pick the best existing package, dry-run it, and apply it only after verification.
Routing:
- For codemod authoring, start with
references/core/create-codemods.md. - If the authoring request implies a monorepo, maintainer workflow, or multi-hop version series, also load
references/core/maintainer-monorepo.md. - For codemod discovery or execution, start with
references/core/search-and-discovery.md. - When moving from discovery to execution, also load
references/core/dry-run-and-verify.mdandreferences/core/scaffold-and-run.md.
Non-negotiable constraints:
- For migration, upgrade, update, or deprecation-rollout requests that do not explicitly ask to create a codemod, search the registry first before proposing a custom codemod plan.
- If registry discovery does not yield a suitable package and the user still needs automation, switch to the codemod-authoring path.
- For codemod authoring, follow the installed creation guidance exactly: stay ast-grep-first, define tests before implementation, keep work inside the requested scope, and do not stop until the package default tests are green.
- For codemod execution, follow the installed runtime guidance exactly: dry-run before apply, verify prerequisites, and prefer the current Codemod CLI help and package docs over guesswork.
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.
- today First seen · 23 lines · 0 tokens per session scan A 9d539dbe847e
codemod is a command published in the GitHub repository vinhnx/vtchat (59 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 373 tokens. 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-10-15.
Other commands, from other repositories
review
Review code changes against project conventions.
gh-triage
GitHub OSS maintainer lifecycle triage, review, and approval management.
check-cache
Audit caching configuration in $ARGUMENTS for Next.js 15 correctness.
server-action
Generate a Server Action for the following mutation: $ARGUMENTS.
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.