seoul-opendata-mcp: Skill for Claude Code

.claude/skills/code-review/SKILL.md

code-review is a skill for Claude Code from whchoi98/seoul-opendata-mcp. It costs 0 tokens per session (646 once invoked), scanned A, original, MIT.

A code-review helper that checks changed files against project rules and looks for likely bugs, security issues, and quality problems. It reports only findings that score as sufficiently credible.

In plain words
What is it for?
Use it to review unstaged Git changes or another selected file range, check project-specific conventions, and receive findings with file locations, explanations, references, and suggested fixes.
Why use it?
It reduces noisy review comments by filtering out likely false alarms. It also helps catch issues such as missing error handling, unsafe secrets, and accessibility problems before they reach users.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

This is whchoi98/seoul-opendata-mcp's own configuration. It tells Claude Code how to work on seoul-opendata-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything seoul-opendata-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to whchoi98/seoul-opendata-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.

Copy the file
curl -O https://raw.githubusercontent.com/whchoi98/seoul-opendata-mcp/main/.claude/skills/code-review/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/whchoi98/seoul-opendata-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for code-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/whchoi98/seoul-opendata-mcp/code-review/github.svg)](https://agentmods.dev/skills/whchoi98/seoul-opendata-mcp/code-review)
Your own site
<a href="https://agentmods.dev/skills/whchoi98/seoul-opendata-mcp/code-review"><img src="https://agentmods.dev/badge/skills/whchoi98/seoul-opendata-mcp/code-review/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.

agentmods 80×15 button for code-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/whchoi98/seoul-opendata-mcp/code-review"><img src="https://agentmods.dev/badge/skills/whchoi98/seoul-opendata-mcp/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 646 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00646
Opus 5 $0.00000 $0.00323
Sonnet 5 $0.00000 $0.00129
Haiku 4.5 $0.00000 $0.00065

Measured 12d ago against content hash c2656bc4aa15, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

code-review 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.

.claude/skills/code-review/SKILL.md · 57 lines

What it actually says

Code Review Skill

변경된 코드를 신뢰도 기반 스코어링으로 검토하여 거짓 양성을 필터링합니다.

검토 범위

기본적으로 git diff의 미스테이징 변경사항을 검토합니다. 사용자가 다른 파일이나 범위를 지정할 수 있습니다.

검토 기준

프로젝트 가이드라인 준수

  • 임포트 패턴 및 모듈 경계
  • 프레임워크 관례 및 언어 스타일
  • 함수 선언 및 에러 처리
  • CLAUDE.md의 명명 규칙

프로젝트 특화 검토 (seoul-opendata-mcp)

  • 픽스처 불변 원칙: tests/fixtures/*.json 파일은 절대 수정하면 안 됨 (실제 API 캡처본, 테스트 데이터 소스)
  • 매핑 동등성 테스트: 정규화 함수(normalize/*.ts)는 API 응답을 표준 포맷으로 변환하고, 역매핑 테스트가 있어야 함
  • 봉투 응답 형식: 모든 MCP 도구 응답은 { ok: true, data: ... } 또는 { ok: false, error: ... } 형식
  • 키 마스킹: 코드/로그에서 API 키 노출 금지 (SEOUL_API_KEY, SEOUL_SUBWAY_API_KEY 등은 환경변수로만)

버그 감지

  • 로직 오류 및 null/undefined 처리
  • 경합 조건 및 메모리 누수
  • 보안 취약점 (OWASP Top 10)
  • 성능 문제

코드 품질

  • 중복 코드 및 불필요한 복잡성
  • 누락된 중요 에러 처리
  • 테스트 커버리지 갭
  • 프런트엔드 접근성 문제

신뢰도 스코어링

각 이슈를 0-100으로 평가합니다:

  • 0-24: 거짓 양성 또는 기존 이슈 가능성. 보고하지 않음.
  • 25-49: 실제일 수도 있지만 사소한 지적. 보고하지 않음.
  • 50-74: 실제 이슈이지만 경미함. 중요한 경우만 보고.
  • 75-89: 검증된 실제 이슈, 중요함. 수정 제안과 함께 보고.
  • 90-100: 확인된 중요 이슈. 반드시 보고.

신뢰도 >= 75인 이슈만 보고합니다.

출력 형식

각 이슈별:

[CRITICAL|IMPORTANT] <이슈 제목> (신뢰도: XX)

파일: 경로/파일.확장자:줄번호 이슈: 문제의 명확한 설명 가이드: CLAUDE.md 규칙 또는 보안 표준 참조 수정: 구체적인 코드 제안

이슈가 없으면 코드가 표준을 충족함을 간략한 요약과 함께 확인하십시오.

Changes

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.

  1. 12d ago First seen · 57 lines · 0 tokens per session scan A c2656bc4aa15

Subscribe to this mod's changes

code-review is a skill published in the GitHub repository whchoi98/seoul-opendata-mcp (1 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 646 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-31.

Related

Other skills, from other repositories

adversarial-reviewer

Adversarial code review that assumes bugs exist and hunts for them. Use when asked to review code, find bugs, audit for correctness, stress-test a PR, or when someone says "tear this apart" or "what's wrong with this". Give no benefit of the doubt — every line is guilty until proven innocent.

emdash-cms/emdash · 71 tokens

gsd-ns-review

Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.

open-gsd/gsd-core · 16 tokens

issue

Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…

jeremylongshore/tons-of-skills-marketplace · 115 tokens

gitnexus

A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.

hashgraph-online/awesome-codex-plugins · 58 tokens

cleanup-code-inspections

Reduce technical debt and improve code quality by systematically resolving static analysis warnings.

flutter/flutter-intellij · 19 tokens

sonarqube-mcp

Provides SonarQube and SonarCloud integration patterns via the Model Context Protocol (MCP) server. Enables quality gate monitoring, issue discovery and triaging, pre-push code analysis, and rule education directly in the agent workflow. Use when the user wants to check quality gates, search for Sonar issues, analyze…

giuseppe-trisciuoglio/developer-kit · 127 tokens