Borrowing it
Nothing to install: this file belongs to isac322/kwin-mcp. 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/isac322/kwin-mcp/main/.claude/skills/release-notes/SKILL.mdgit clone --depth 1 https://github.com/isac322/kwin-mcpWrote 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/isac322/kwin-mcp/release-notes)<a href="https://agentmods.dev/skills/isac322/kwin-mcp/release-notes"><img src="https://agentmods.dev/badge/skills/isac322/kwin-mcp/release-notes/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/isac322/kwin-mcp/release-notes"><img src="https://agentmods.dev/badge/skills/isac322/kwin-mcp/release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 34 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- low MCP Rug Pull · line 69 pip install without ==version installs the latest release, which could include malicious changes.Fix: Pin the version: pip install package==1.2.3
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.00976 |
| Opus 5.5 | $0.00000 | $0.00390 |
| Sonnet 5.5 | $0.00000 | $0.00195 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
release-notes 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 12d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Generator
Generate SEO-optimized GitHub release notes for kwin-mcp.
Usage
/release-notes <version>
Example: /release-notes v1.0.0
Instructions
Step 1: Gather Context
- Read
CHANGELOG.mdand find the entry for the specified version - Read
pyproject.tomlto confirm the current version and project metadata - Check existing GitHub releases for style consistency:
gh release list --limit 5 gh release view <previous-version>
Step 1.5: Verify plugin manifests + bundled SKILL.md are in sync
Before generating release notes, ensure all integrations (.claude-plugin/marketplace.json, integrations/claude-code/.claude-plugin/plugin.json, integrations/opencode/plugin/package.json, and the OpenCode plugin's bundled SKILL.md) reflect the version being released:
python3 scripts/sync_plugin_version.py # write synced state
python3 scripts/sync_plugin_version.py --check # verify (CI also runs this)
If new MCP tools were added or renamed in this release, also confirm that integrations/claude-code/skills/kwin-desktop-automation/SKILL.md reflects them — the OpenCode plugin auto-mirrors that file on its next npm run build. The release notes' New Tools table should match what the SKILL.md exposes.
Step 2: Determine Release Type
- Patch release (x.y.Z): bug fixes, minor improvements
- Minor release (x.Y.0): new features, new tools, non-breaking changes
- Major release (X.0.0): breaking changes
Step 3: Generate Release Notes
Minor+ Release Template
kwin-mcp vX.Y.Z <one-line value proposition with primary keywords>.
## Highlights
- **Feature name**: Description mentioning exact technology (AT-SPI2, libei, EIS, D-Bus, etc.)
- **Feature name**: Description with concrete numbers (e.g. "29 MCP tools")
- ...
## New Tools
| Tool | Description |
|------|-------------|
| `tool_name` | What it does |
| ... | ... |
## Installation
\```bash
# Using uv (recommended)
uv tool install kwin-mcp
# Using pip
pip install kwin-mcp
\```
**Full Changelog**: https://github.com/isac322/kwin-mcp/compare/vPREVIOUS...vCURRENT
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.
- 12d ago Changed a79a3651a39e
- 1mo ago First seen · 105 lines · 0 tokens per session scan A 134e0f5a6897
release-notes is a skill published in the GitHub repository isac322/kwin-mcp (77 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 976 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-08-30.
Other skills, from other repositories
ship
Pre-release gate. Run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.
kb-github-a11y-scanner
Reference data, not a reviewer. Integrate GitHub Accessibility Scanner. Detects configuration, parses scanner issues, correlates with local scans, and tracks Copilot-assigned fixes.
daily-briefing
Daily GitHub briefing: issues, PRs, reviews, releases and discussions.
release-manager
GitHub releases: create, edit and manage releases and their assets.
tadado-release
A release checklist for the Tadado2 repository. It defines how to test, package, commit, push, tag, publish a GitHub Release, and synchronize the local skill files.
release
Release preparation workflow - security audit → E2E tests → review → changelog → docs.