difit is a command-line tool that starts a local web server showing Git commit differences in a GitHub-style file-change viewer. Developers use it to inspect and review local diffs or pull requests, with review comments that can also be copied into AI prompts. The catalogue entries connect coding-agent workflows to difit for requesting or performing reviews.
Borrowing it
Nothing to install: this file belongs to yoshiko-pg/difit. 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/yoshiko-pg/difit/main/.codex/skills/vscode-release/SKILL.mdgit clone --depth 1 https://github.com/yoshiko-pg/difitWrote 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/yoshiko-pg/difit/vscode-release)<a href="https://agentmods.dev/skills/yoshiko-pg/difit/vscode-release"><img src="https://agentmods.dev/badge/skills/yoshiko-pg/difit/vscode-release/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/skills/yoshiko-pg/difit/vscode-release"><img src="https://agentmods.dev/badge/skills/yoshiko-pg/difit/vscode-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00049 | $0.00488 |
| Opus 5.5 | $0.00020 | $0.00195 |
| Sonnet 5.5 | $0.00010 | $0.00098 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
vscode-release 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 2mo 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.
What it actually says
VS Code Extension Release Workflow
Follow this workflow for the current repository.
Prepare local build verification
- Verify release target files in
packages/vscodeand confirm current branch state. - Run
pnpm install --frozen-lockfile. - Run
pnpm -C packages/vscode run package. - Read
packages/vscode/package.jsonand confirm the current extension version. - Confirm the VSIX exists at
packages/vscode/difit-vscode-<version>.vsix. - Ask the user to smoke test the local VSIX install in VS Code:
- Install from VSIX.
- Confirm the
difitcommand opens review correctly. - Confirm the toolbar button/icon appears and works.
- Ask for explicit OK in Japanese before publishing.
Release after explicit OK
Treat the locally verified build result at OK time as the source of truth. Do not skip rebuilding after version changes.
- Bump extension version in
packages/vscode/package.json:pnpm -C packages/vscode version patch --no-git-tag-version
- Re-run
pnpm -C packages/vscode run packageand confirm the new VSIX filename. - Commit
packages/vscode/package.jsonwith an English message:chore(vscode): release vX.Y.Z. - Create tag
vscode-vX.Y.Z. - Push
mainand tags:git push origin main --tags. - If push is rejected by non-fast-forward:
- Run
git pull --rebase origin main. - Retry
git push origin main --tags.
- Run
- Publish to Visual Studio Marketplace:
pnpm -C packages/vscode exec vsce publish- Use the already bumped version from
packages/vscode/package.json.
Output to user
- Respond in Japanese.
- Report local build verification result, released version, created tag, and publish result.
- Mention if any recovery step was required (for example, rebase due to non-fast-forward).
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 47 lines · 49 tokens per session scan A eec8868a13fa
vscode-release is a skill published in the GitHub repository yoshiko-pg/difit (3,296 stars, last pushed 2mo ago), licensed MIT. It adds 49 tokens to every session and 488 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.