Claude Code Viewer is a web client for managing Claude Code projects, including starting or resuming conversations, monitoring tasks, and browsing session history. Its catalogue entries provide skills, commands, hooks, instructions, and settings that extend the client’s workflow.
Borrowing it
Nothing to install: this file belongs to d-kimuson/claude-code-viewer. 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/d-kimuson/claude-code-viewer/main/.claude/commands/refine-release-note.mdgit clone --depth 1 https://github.com/d-kimuson/claude-code-viewerWrote 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/d-kimuson/claude-code-viewer/refine-release-note)<a href="https://agentmods.dev/commands/d-kimuson/claude-code-viewer/refine-release-note"><img src="https://agentmods.dev/badge/commands/d-kimuson/claude-code-viewer/refine-release-note/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/d-kimuson/claude-code-viewer/refine-release-note"><img src="https://agentmods.dev/badge/commands/d-kimuson/claude-code-viewer/refine-release-note.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.00019 | $0.00390 |
| Opus 5.5 | $0.00008 | $0.00156 |
| Sonnet 5.5 | $0.00004 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
refine-release-note 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 1mo 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
Review and refine the latest version section in CHANGELOG.md to make it suitable for a release announcement.
Scope
Focus only on the most recent version section (the first version block in CHANGELOG.md).
Principles
<user_facing_content>
Keep User-Facing Changes Only
Include changes that matter to end users:
- New features and capabilities
- Bug fixes that affect user experience
- Performance improvements users will notice
- Breaking changes or deprecations
Remove internal/development changes:
- CI/CD configuration changes
- Internal refactoring
- Development tooling additions
- Dependency updates (unless they fix security issues or add user-visible features)
- Test improvements
- Documentation fixes
- Linting and formatting changes </user_facing_content>
<writing_style>
Release Note Writing Style
- Use clear, concise descriptions focused on user benefits
- Combine related commits into single, meaningful entries
- Remove redundant or overly technical details
- Ensure descriptions are self-explanatory without commit context
- Maintain consistent tone and formatting with previous releases </writing_style>
Workflow
- Read CHANGELOG.md: Identify the latest version section
- Analyze each entry: Determine if it's user-facing or internal
- Edit CHANGELOG.md:
- Remove internal/development entries
- Refine remaining entries for clarity
- Combine related changes where appropriate
- Report: Summarize what was removed and why
Error Handling
- If CHANGELOG.md doesn't exist, inform the user
- If the latest version has no entries, report this
- If all entries are internal changes, note that this might be a maintenance release
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.
- 1mo ago First seen · 62 lines · 19 tokens per session scan A b7568a7e26a8
refine-release-note is a command published in the GitHub repository d-kimuson/claude-code-viewer (1,300 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 390 once invoked, about $0.0001 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 commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
rally-merge-pr
You are merging the current branch's PR and syncing the feature branch with main. Follow each step exactly.