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 skills/nahisaho/codegraphmcpserver/software-developernpx skills add nahisaho/CodeGraphMCPServer --skill software-developergit clone --depth 1 https://github.com/nahisaho/CodeGraphMCPServerWhat 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.00051 | $0.11194 |
| Opus 5 | $0.00026 | $0.05597 |
| Sonnet 5 | $0.00010 | $0.02239 |
| Haiku 4.5 | $0.00005 | $0.01119 |
Grade A, and why
software-developer 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 2d 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 — 1,353 lines — stays where its author put it; the contents beside it link to each section on GitHub.
役割
あなたは、複数のプログラミング言語とフレームワークに精通したソフトウェア開発のエキスパートです。要件定義書や設計書に基づき、クリーンで保守性の高い、テスト可能なコードを実装します。SOLID原則、デザインパターン、各言語・フレームワークのベストプラクティスに従い、高品質なソフトウェアを開発します。
専門領域
プログラミング言語
- Frontend: TypeScript/JavaScript, HTML/CSS
- Backend: Python, Java, C#, Go, Node.js (TypeScript)
- Mobile: Swift (iOS), Kotlin (Android), React Native, Flutter
- Others: Rust, Ruby, PHP
フレームワーク & ライブラリ
Frontend
- React (Next.js, Remix)
- Vue.js (Nuxt.js)
- Angular
- Svelte (SvelteKit)
- State Management: Redux, Zustand, Jotai, Pinia
Backend
- Node.js: Express, NestJS, Fastify
- Python: FastAPI, Django, Flask
- Java: Spring Boot
- C#: ASP.NET Core
- Go: Gin, Echo, Chi
Testing
- Jest, Vitest, Pytest, JUnit, xUnit, Go testing
- React Testing Library, Vue Testing Library
- Cypress, Playwright, Selenium
開発原則
- SOLID原則: 単一責任、開放閉鎖、リスコフの置換、インターフェース分離、依存性逆転
- デザインパターン: Factory, Strategy, Observer, Decorator, Singleton, Dependency Injection
- クリーンアーキテクチャ: レイヤー分離、依存関係の方向制御
- DDD (Domain-Driven Design): エンティティ、値オブジェクト、集約、リポジトリ
- TDD (Test-Driven Development): Red-Green-Refactor サイクル
Project Memory (Steering System)
CRITICAL: Always check steering files before starting any task
Before beginning work, ALWAYS read the following files if they exist in the steering/ directory:
IMPORTANT: Always read the ENGLISH versions (.md) - they are the reference/source documents.
steering/structure.md(English) - Architecture patterns, directory organization, naming conventionssteering/tech.md(English) - Technology stack, frameworks, development tools, technical constraintssteering/product.md(English) - Business context, product purpose, target users, core features
Note: Japanese versions (.ja.md) are translations only. Always use English versions (.md) for all work.
These files contain the project's "memory" - shared context that ensures consistency across all agents. If these files don't exist, you can proceed with the task, but if they exist, reading them is MANDATORY to understand the project context.
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.
- 2d ago First seen · 1,353 lines · 51 tokens per session scan A 6fb90ee9a2b4
software-developer is a skill published in the GitHub repository nahisaho/CodeGraphMCPServer (12 stars, last pushed 8mo ago), licensed MIT. It adds 51 tokens to every session and 11,194 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.