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 mcp/bartstc/vite-ts-react-template/githubgit clone --depth 1 https://github.com/bartstc/vite-ts-react-templateGrade A, and why
github 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
88% identical to github — 4 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.
What it actually says
{
"github": {
"type": "stdio",
"command": "pnpm",
"args": [
"dlx",
"@modelcontextprotocol/server-github"
],
"env": {
"GITHUB_PERSONAL_ACCESS_TOKEN": "${GITHUB_PERSONAL_ACCESS_TOKEN}"
}
}
}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 · 13 lines scan A 12a60fa06212
github is an MCP server published in the GitHub repository bartstc/vite-ts-react-template (121 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. It is 88% identical to github, differing in 4 lines, and is treated as a copy.
Other mcp servers, from other repositories
next-devtools
Next.js development tools MCP server with stdio transport. Runs locally from the next-devtools-mcp npm package.
codegraph
MCP server "codegraph" as configured in webiny/webiny-js. Launched with codegraph serve --mcp.
atlassian
MCP server "atlassian", hosted remotely at mcp.atlassian.com, as configured in instructure/instructure-ui.
airjam
MCP server "airjam" as configured in vucinatim/air-jam. Launched with pnpm mcp.
shadcn
Add components to your apps. Runs locally from the shadcn npm package.
vitex
Generate tailored, ATS-optimized resume PDFs and cover letters from a job description, over MCP. Runs locally from the vitex-cli npm package. Needs 1 environment variable to run.