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/utenadev/qwencode-mcp-server/claude-mdgit clone --depth 1 https://github.com/utenadev/qwencode-mcp-serverWrote 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/utenadev/qwencode-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/utenadev/qwencode-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/utenadev/qwencode-mcp-server/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.01716 | $0.01716 |
| Opus 5 | $0.00858 | $0.00858 |
| Sonnet 5 | $0.00343 | $0.00343 |
| Haiku 4.5 | $0.00172 | $0.00172 |
Grade A, and why
qwencode-mcp-server CLAUDE.md 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
プロジェクト概要
QwenCode MCP Server は、Model Context Protocol (MCP) を使用して AI アシスタントが Qwen AI モデルと対話できるようにするサーバーです。
現在、このプロジェクトは単一目的の Qwen ツールから、汎用の AI プロバイダーフレームワークへの移行が進行中です(docs/PLAN.md および docs/ROADMAP.md を参照)。
開発コマンド
# ビルド
npm run build
# 開発(ビルドして実行)
npm run dev
# 実行(ビルド済み)
npm start
# テスト実行
npm test
# リント(TypeScript 型チェックのみ)
npm run lint
# 単一のテストファイルを実行
node --test test/tools.test.js
node --test test/registry.test.js
アーキテクチャ
メタデータ駆動設計
プロジェクトの核となる概念は、CLI ツールの機能をメタデータとして記述し、そこから MCP ツールを動的に生成することです。
CliToolMetadata → DynamicToolFactory → MCP Tool
コアコンポーネント
| コンポーネント | 役割 | ファイル |
|---|---|---|
AIProvider |
全プロバイダーの共通インターフェース | src/providers/base-cli.provider.ts |
BaseCliProvider |
CLI ベースプロバイダーの抽象基底クラス | src/providers/base-cli.provider.ts |
QwenProvider |
Qwen の具象実装 | src/providers/qwen.provider.ts |
CliToolMetadata |
CLI ツールの機能を記述する型 | src/types/cli-metadata.ts |
DynamicToolFactory |
メタデータから MCP ツールを生成 | src/tools/dynamic-tool-factory.ts |
toolRegistry |
登録されたツールの一元管理 | src/tools/registry.ts |
ツール登録の流れ
src/tools/index.tsでプロバイダーをインスタンス化registerProvider(new QwenProvider())で登録DynamicToolFactoryがメタデータから Zod スキーマと実行ロジックを生成- MCP サーバーがツール定義をクライアントに公開
進行中のリファクタリング(Phase 1-3)
- Phase 1: 基盤となる型とクラス構造の確立(完了)
- Phase 2: 既存の Qwen ロジックを新しい構造に移行(完了)
- Phase 3: メインアプリケーションフローとの統合(完了)
将来のロードマップ(Phase 4+)
- HelpParser: CLI
--help出力からメタデータを自動生成 - 汎用プロバイダー: OpenAI、Ollama、Anthropic などのサポート
- 設定ファイル駆動: ユーザーがコードを変更せずにツールを追加可能に
ファイル構成
src/
├── index.ts # MCP サーバーのエントリーポイント
├── constants.ts # 定数・型定義
├── types/
│ └── cli-metadata.ts # CliToolMetadata、CliOption などの型
├── providers/
│ ├── base-cli.provider.ts # AIProvider インターフェース、BaseCliProvider
│ └── qwen.provider.ts # QwenProvider の実装
├── tools/
│ ├── index.ts # ツール登録のエントリーポイント
│ ├── registry.ts # toolRegistry、registerProvider
│ ├── dynamic-tool-factory.ts # メタデータからツールを生成
│ ├── simple-tools.ts # Ping、Help などの静的ツール
│ └── ask-qwen.tool.ts # (非推奨)QwenProvider に置換済み
└── utils/
├── commandExecutor.ts # CLI コマンド実行(10分タイムアウト)
├── logger.ts # ログ出力(NO_COLOR 対応)
└── progressManager.ts # MCP 進行状況通知
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.
- 4d ago First seen · 163 lines · 1,716 tokens per session scan A d143ae7b4cb8
qwencode-mcp-server CLAUDE.md is an instructions file published in the GitHub repository utenadev/qwencode-mcp-server (1 stars, last pushed 7mo ago), licensed MIT. It adds 1,716 tokens to every session, about $0.0086 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 instructions, from other repositories
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.