Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/peakflames/polarionmcpservers/releasegit clone --depth 1 https://github.com/peakflames/PolarionMcpServersWrote 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/peakflames/polarionmcpservers/release)<a href="https://agentmods.dev/commands/peakflames/polarionmcpservers/release"><img src="https://agentmods.dev/badge/commands/peakflames/polarionmcpservers/release.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.00013 | $0.00516 |
| Opus 5 | $0.00006 | $0.00258 |
| Sonnet 5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
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 5d 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
Release Process
You are performing a release from develop to main. Follow these steps exactly:
Step 1: Verify Clean State
- Check git status on develop branch
- Ensure there are no uncommitted changes (except appsettings.Development.json)
- Ensure develop is pushed to origin
Step 2: Get Current Version
- Read the
<Version>tag fromPolarionRemoteMcpServer/PolarionRemoteMcpServer.csproj - This is the version being released (e.g.,
0.12.0)
Step 3: Merge to Main
git checkout main
git pull origin main
git merge develop --no-ff -m "Merge branch 'develop' into main for v{VERSION} release"
Step 4: Tag the Release
git tag -a v{VERSION} -m "Release v{VERSION}"
Step 5: Push Main and Tag
git push origin main
git push origin v{VERSION}
Note: GitHub Actions will automatically create the release and publish artifacts when the tag is pushed.
Step 6: Prepare Develop for Next Version
- Checkout develop
- Calculate next version by incrementing minor version (e.g.,
0.12.0→0.13.0) - Update
PolarionRemoteMcpServer/PolarionRemoteMcpServer.csproj:- Set
<Version>to next version - Set
<ContainerImageTag>to next version
- Set
- Update
CHANGELOG.md:- Add new section at top:
## {NEXT_VERSION} (In Development)\n\nChanges TBD\n\n
- Add new section at top:
Step 7: Commit and Push Develop
git add PolarionRemoteMcpServer/PolarionRemoteMcpServer.csproj CHANGELOG.md
git commit -m "chore: bump version to {NEXT_VERSION} for development
Co-Authored-By: Claude Opus 4.5 <[email protected]>"
git push origin develop
Important Notes
- NEVER commit
appsettings.Development.json - Use
--no-fffor merge to preserve commit history - Tag format is
v{VERSION}(e.g.,v0.12.0) - Always confirm version numbers with the user before proceeding
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.
- 5d ago First seen · 60 lines · 13 tokens per session scan A ab1c6ecff15d
release is a command published in the GitHub repository peakflames/PolarionMcpServers (38 stars, last pushed 12d ago), licensed MIT. It adds 13 tokens to every session and 516 once invoked, about $0.0001 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-30.
Other commands, from other repositories
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release
Create a release branch, run changeset version, review changelog, and prepare PR.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
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.