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.
git clone --depth 1 https://github.com/HanHyeong/jira-wiki-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/rules/hanhyeong/jira-wiki-mcp/version-changelog)<a href="https://agentmods.dev/rules/hanhyeong/jira-wiki-mcp/version-changelog"><img src="https://agentmods.dev/badge/rules/hanhyeong/jira-wiki-mcp/version-changelog/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/rules/hanhyeong/jira-wiki-mcp/version-changelog"><img src="https://agentmods.dev/badge/rules/hanhyeong/jira-wiki-mcp/version-changelog.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.00342 | $0.00342 |
| Opus 5 | $0.00171 | $0.00171 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
version-changelog 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 9d 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
버전·변경 이력 (필수)
이 저장소에서 기능·동작·공개 API에 영향을 주는 수정을 마칠 때는 같은 작업 안에서 아래를 수행한다.
-
project_version.py의__version__- 기본은 패치 증가 (예:
1.2.0→1.2.1). - 사용자가 major/minor 릴리스를 요청한 경우에만 그에 맞게 올린다.
- 기본은 패치 증가 (예:
-
CHANGELOG.md- 새 버전이면
## [x.y.z] — YYYY-MM-DD섹션을 추가하고,[Unreleased]는 비우거나 남긴다. - 변경 요약을 bullet로 적는다 (도구 추가, 버그 수정, 의존성 변경 등).
- 새 버전이면
-
버전을 올리지 않아도 되는 경우
- 순수 오타·문장만 고치는 Markdown, 코드 의미 없는 공백만, 규칙/가이드의 표현만 살짝 다듬은 수준.
-
반드시 패치 이상 올릴 것
*.py로직 변경, MCP 도구 추가/스키마 변경,requirements.txt/pyproject.toml의존성 변경, CLI 동작 변경.
에이전트는 작업 완료 전에 __version__과 CHANGELOG 반영 여부를 스스로 확인한다.
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.
- 9d ago First seen · 25 lines · 342 tokens per session scan A faa1f3fc0da8
version-changelog is a cursor rule published in the GitHub repository HanHyeong/jira-wiki-mcp (2 stars, last pushed 4mo ago), licensed MIT. It adds 342 tokens to every session, about $0.0017 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-31.
Other cursor rules, from other repositories
monorepo-versioning
Internal peerDependency ranges and Changesets conventions for the SDK monorepo — avoid major-version cascades.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
release-checklist
What to update with each code change or version release.
release-policy
Release, versioning, and signing policy for setmac.
bump-project-version
The user can provide version in one of three ways.