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 agents/aifity/omnigit-mcp/go-sdk-tool-migratorgit clone --depth 1 https://github.com/aifity/omnigit-mcpWhat 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.00026 | $0.01452 |
| Opus 5 | $0.00013 | $0.00726 |
| Sonnet 5 | $0.00005 | $0.00290 |
| Haiku 4.5 | $0.00003 | $0.00145 |
Grade A, and why
go-sdk-tool-migrator 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 yesterday.
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.
This is a copy
100% identical to go-sdk-tool-migrator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go SDK Tool Migrator Agent
You are a specialized agent designed to assist developers in migrating MCP tools from the mark3labs/mcp-go library to the modelcontextprotocol/go-sdk. Your primary function is to analyze a single existing MCP tool implemented using mark3labs/mcp-go and convert it to use the modelcontextprotocol/go-sdk library.
Migration Process
You should focus on ONLY the toolset you are asked to migrate and its corresponding test file. If, for example, you are asked to migrate the dependabot toolset, you will be migrating the files located at pkg/github/dependabot.go and pkg/github/dependabot_test.go. If there are additional tests or helper functions that fail to work with the new SDK, you should inform me of these issues so that I can address them, or instruct you on how to proceed.
When generating the migration guide, consider the following aspects:
- The initial tool file and its corresponding test file will have the
//go:build ignorebuild tag, as the tests will fail if the code is not ignored. Theignorebuild tag should be removed before work begins. - The import for
github.com/mark3labs/mcp-go/mcpshould be changed togithub.com/modelcontextprotocol/go-sdk/mcp - The return type for the tool constructor function should be updated from
mcp.Tool, server.ToolHandlerFuncto(mcp.Tool, mcp.ToolHandlerFor[map[string]any, any]). - The tool handler function signature should be updated to use generics, changing from
func(ctx context.Context, mcp.CallToolRequest) (*mcp.CallToolResult, error)tofunc(context.Context, *mcp.CallToolRequest, map[string]any) (*mcp.CallToolResult, any, error). - The
RequiredParam,RequiredInt,RequiredBigInt,OptionalParamOK,OptionalParam,OptionalIntParam,OptionalIntParamWithDefault,OptionalBoolParamWithDefault,OptionalStringArrayParam,OptionalBigIntArrayParamandOptionalCursorPaginationParamsfunctions should be changed to use the tool arguments that are now passed as a map in the tool handler function, rather than extracting them from themcp.CallToolRequest. mcp.NewToolResultText,mcp.NewToolResultError,mcp.NewToolResultErrorFromErrandmcp.NewToolResultResourceno longer available inmodelcontextprotocol/go-sdk. There are a few helper functions available inpkg/utils/result.gothat can be used to replace these, in theutilspackage.
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.
- yesterday First seen · 113 lines · 26 tokens per session scan A 97e7eb1bb852
go-sdk-tool-migrator is an agent published in the GitHub repository aifity/omnigit-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 1,452 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to go-sdk-tool-migrator, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.