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 instructions/minami110/mcp-gdscript/claude-mdgit clone --depth 1 https://github.com/minami110/mcp-gdscriptWrote 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/instructions/minami110/mcp-gdscript/claude-md)<a href="https://agentmods.dev/instructions/minami110/mcp-gdscript/claude-md"><img src="https://agentmods.dev/badge/instructions/minami110/mcp-gdscript/claude-md.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 | $0.01393 | $0.01393 |
| Opus 5 | $0.00696 | $0.00696 |
| Sonnet 5 | $0.00279 | $0.00279 |
| Haiku 4.5 | $0.00139 | $0.00139 |
Grade C, and why
mcp-gdscript CLAUDE.md scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .venv How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mcp-gdscript 開発ガイド
このファイルはプロジェクト開発時の動作確認と トラブルシューティング手順を記載しています。
動作確認手順
1. ローカル開発環境での確認
推奨: uv を使用(グローバル環境を汚さない)
# uv 環境でサーバー起動テスト
uv run mcp-gdscript
予想される出力:
- MCP サーバーが起動し、標準入力からのメッセージを待機する状態になります
2. uvx での直接実行確認
GitHub からのインストール版を直接テストできます:
# 最新版を uvx で実行
uvx mcp-gdscript@git+https://github.com/minami110/mcp-gdscript
# または PyPI リリース版を実行(リリース後)
uvx mcp-gdscript
依存関係エラーの対処
エラー例:
× No solution found when resolving tool dependencies:
╰─▶ Because there is no version of mcp==1.3.1 ...
原因: pyproject.toml で指定されている mcp のバージョンが存在しない
解決方法:
pyproject.tomlのdependenciesセクションを確認- mcp バージョンを最新の安定版に更新
# 修正前
dependencies = [
"mcp==1.3.1", # ❌ このバージョンは存在しない
"tree-sitter-language-pack==0.3.9",
]
# 修正後
dependencies = [
"mcp>=1.19.0", # ✅ 最新の安定版を指定
"tree-sitter-language-pack==0.3.9",
]
利用可能なバージョンは PyPI mcp で確認できます。
3. 他プロジェクトでの利用確認
別のプロジェクトで MCP サーバーとして利用する場合:
設定ファイル: .claude/mcp.json または ~/.claude/mcp.json
{
"mcpServers": {
"gdscript": {
"command": "uvx",
"args": ["mcp-gdscript@git+https://github.com/minami110/mcp-gdscript"]
}
}
}
利用確認方法
- Claude コード内で確認
- 以下のコマンドで CLI から確認:
# mcp.json が有効か確認
cd /path/to/another-project
uvx mcp-gdscript@git+https://github.com/minami110/mcp-gdscript
トラブルシューティング
エラー: "Module not found: mcp"
原因: 依存パッケージがインストールされていない
解決方法:
# uv で依存関係を再解決
uv sync
# または uv で実行
uv run mcp-gdscript
エラー: "Python version 3.10 or higher required"
原因: Python バージョンが 3.10 未満
確認方法:
python --version # 3.10 以上である必要があります
解決方法:
uv は Python バージョンの管理も含まれているため、以下で自動的に解決されます:
uv run mcp-gdscript # 必要な Python バージョンがあれば自動検出
手動で Python 3.10+ に切り替える場合:
# Python 3.10 が利用可能か確認
python3.10 --version
# Python 3.10 を指定して実行
uv run --python 3.10 mcp-gdscript
エラー: "tree-sitter-language-pack version mismatch"
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 · 185 lines · 1,393 tokens per session scan C 912a1d20e836
mcp-gdscript CLAUDE.md is an instructions file published in the GitHub repository minami110/mcp-gdscript (1 stars, last pushed 10mo ago), licensed MIT. It adds 1,393 tokens to every session, about $0.0070 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).