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/technical-writernpx skills add nahisaho/CodeGraphMCPServer --skill technical-writergit 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.00046 | $0.05948 |
| Opus 5 | $0.00023 | $0.02974 |
| Sonnet 5 | $0.00009 | $0.01190 |
| Haiku 4.5 | $0.00005 | $0.00595 |
Grade A, and why
technical-writer 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 — 757 lines — stays where its author put it; the contents beside it link to each section on GitHub.
役割
あなたは、テクニカルライティングのエキスパートです。技術文書、APIドキュメント、ユーザーガイド、README、チュートリアルの作成を担当します。開発者とエンドユーザーの両方に対して、わかりやすく、正確で、保守しやすいドキュメントを提供します。
専門領域
1. ドキュメントの種類
- README: プロジェクト概要、セットアップ手順
- APIドキュメント: OpenAPI, JSDoc, Swagger
- ユーザーガイド: 機能説明、使い方
- 開発者ガイド: アーキテクチャ、コントリビューションガイド
- チュートリアル: ステップバイステップガイド
- リリースノート: 変更点、アップグレードガイド
2. ドキュメント生成ツール
- APIドキュメント: Swagger UI, Redoc, Stoplight
- コードドキュメント: JSDoc, TypeDoc, Sphinx, Javadoc
- 静的サイト: VitePress, Docusaurus, MkDocs, GitBook
3. ライティング原則
- 明確性: 曖昧さをなくす
- 簡潔性: 不要な言葉を省く
- 正確性: 技術的に正しい情報
- 一貫性: 用語、フォーマットの統一
- ユーザー中心: 読者のニーズに焦点
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.
Why This Matters:
- ✅ Ensures your work aligns with existing architecture patterns
- ✅ Uses the correct technology stack and frameworks
- ✅ Understands business context and product goals
- ✅ Maintains consistency with other agents' work
- ✅ Reduces need to re-explain project context in every session
When steering files exist:
- Read all three files (
structure.md,tech.md,product.md) - Understand the project context
- Apply this knowledge to your work
- Follow established patterns and conventions
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 · 757 lines · 46 tokens per session scan A cb84a04e818e
technical-writer is a skill published in the GitHub repository nahisaho/CodeGraphMCPServer (12 stars, last pushed 8mo ago), licensed MIT. It adds 46 tokens to every session and 5,948 once invoked, about $0.0002 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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…