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 skills add This-HW/claude-code-kit --skill mcp-buildergit clone --depth 1 https://github.com/This-HW/claude-code-kitWrote 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/this-hw/claude-code-kit/mcp-builder)<a href="https://agentmods.dev/skills/this-hw/claude-code-kit/mcp-builder"><img src="https://agentmods.dev/badge/skills/this-hw/claude-code-kit/mcp-builder/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/this-hw/claude-code-kit/mcp-builder"><img src="https://agentmods.dev/badge/skills/this-hw/claude-code-kit/mcp-builder.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.00028 | $0.01069 |
| Opus 5.5 | $0.00011 | $0.00428 |
| Sonnet 5.5 | $0.00006 | $0.00214 |
| Haiku 4.5 | $0.00003 | $0.00107 |
Grade B, and why
mcp-builder scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`~/.claude/settings.json`: How it starts
The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server Builder
Model Context Protocol 서버 개발 및 구성
MCP 서버를 생성하고 Claude Code에 통합합니다.
사용법
신규 MCP 서버 생성
/mcp-builder "파일 시스템 접근" filesystem
/mcp-builder "데이터베이스 조회" database-query
/mcp-builder "API 통합" external-api
기존 MCP 서버 설정
/mcp-builder setup postgres
/mcp-builder configure playwright
MCP 서버 유형
1. Tools 서버
외부 도구 및 API 접근:
- 데이터베이스 쿼리
- 파일 시스템 조작
- 외부 API 호출
- 시스템 명령 실행
2. Resources 서버
정적 리소스 제공:
- 문서 검색
- 설정 파일 읽기
- 템플릿 제공
3. Prompts 서버
사전 정의된 프롬프트:
- 재사용 가능한 질의
- 템플릿 프롬프트
개발 워크플로우
1. 프로젝트 초기화
# Python MCP 서버
mkdir mcp-server-myproject
cd mcp-server-myproject
python -m venv venv
source venv/bin/activate
pip install mcp
2. 서버 구조 생성
mcp-server-myproject/
├── src/
│ ├── __init__.py
│ └── server.py # MCP 서버 구현
├── pyproject.toml # 의존성
└── README.md # 사용법
3. Tools 정의
from mcp import Server, Tool
server = Server("myproject-server")
@server.tool()
async def my_tool(arg1: str, arg2: int) -> str:
"""도구 설명"""
# 구현
return result
4. 서버 실행
if __name__ == "__main__":
server.run()
Claude Code 통합
1. MCP 설정 파일 수정
~/.claude/settings.json:
{
"mcpServers": {
"myproject": {
"command": "python",
"args": ["-m", "mcp_server_myproject"],
"env": {
"API_KEY": "your-key"
}
}
}
}
2. 서버 시작
claude mcp list # MCP 서버 목록 확인
claude mcp --help # 가용 서브커맨드 확인(버전마다 달라질 수 있음)
템플릿
Python MCP Tools 서버
from mcp import Server
from typing import Any
server = Server("example-server")
@server.tool()
async def example_tool(
param1: str,
param2: int = 10
) -> dict[str, Any]:
"""
Example tool description.
Args:
param1: First parameter
param2: Second parameter (default: 10)
Returns:
Result dictionary
"""
return {
"result": f"Processed {param1} with {param2}",
"status": "success"
}
if __name__ == "__main__":
server.run()
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 Changed 6f0ad2bbc22a
- 1mo ago First seen · 236 lines · 28 tokens per session scan B 744272c1c8fa
mcp-builder is a skill published in the GitHub repository This-HW/claude-code-kit (4 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 1,069 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
code-standards
Prabhdeep (Sonu) Singh's personal coding standards — the house rules and quality bar for how code gets written. INVOKE before writing, generating, refactoring, or reviewing ANY code in ANY language — schemas, endpoints, queries, logging, validation, error handling — even when nobody says "standards" or "style".…
design-tree
Make design decisions as an explicit branching tree — genuine alternatives, decisive rationale, rejected branches preserved. INVOKE PROACTIVELY when planning or designing any implementation approach, or choosing between architectures, libraries, or data models — especially in plan mode. Skip trivial or forced changes…
self-review
Surface the riskiest parts of the current diff so a reviewer knows where to look hardest — one inline pass on small diffs, one cold read on a cheaper model tier with in-session synthesis on substantial ones. INVOKE PROACTIVELY whenever a change is finished and about to be handed off, reviewed, or shipped. It points…
ticket-lifecycle
The ticket-as-control-plane rulebook — the single home for the tracker-operations contract, tracker resolution, the type/priority taxonomy, human-only trigger authorization, derived status, and trust boundaries. INVOKE when reading or writing tickets in a queue-driven flow, resolving a repo's tracker, or deciding…
tdd
Test-driven development — the red-green-refactor discipline for code that's correct by design, not by accident. INVOKE PROACTIVELY whenever writing or changing code, fixing a bug, adding or structuring tests, or choosing what to mock — even when nobody says "TDD" or "tests". (Tests are code held to…
pr-conventions
Author PR descriptions from the right per-change-type template (the repo's own PULLREQUESTTEMPLATE wins), embed issue-tracker links, keep the description current as fixes land, and reply to human and bot review threads. INVOKE when opening or updating a PR or responding to reviewer comments — inside /sonu:ship or…