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.
git clone --depth 1 https://github.com/Lykhoyda/ask-llmWrote 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/mcp/lykhoyda/ask-llm/antigravity-mcp-ask-grok)<a href="https://agentmods.dev/mcp/lykhoyda/ask-llm/antigravity-mcp-ask-grok"><img src="https://agentmods.dev/badge/mcp/lykhoyda/ask-llm/antigravity-mcp-ask-grok/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/lykhoyda/ask-llm/antigravity-mcp-ask-grok"><img src="https://agentmods.dev/badge/mcp/lykhoyda/ask-llm/antigravity-mcp-ask-grok.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ask-grok 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 1mo 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.
What it actually says
{
"ask-grok": {
"command": "npx",
"args": [
"-y",
"@ask-llm/grok-mcp"
],
"env": {
"XAI_API_KEY": "",
"ASK_GROK_HARNESS": "xai-api",
"ASK_GROK_MODEL": "",
"ASK_GROK_REASONING_EFFORT": "high",
"ASK_GROK_MAX_OUTPUT_TOKENS": "16384",
"ASK_GROK_TIMEOUT_MS": "600000",
"GMCPT_LOG_LEVEL": "warn"
}
}
}What else server.json configures
This page is one entry in a file that holds 7. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 1mo ago First seen · 18 lines scan A 8a6d7fc82126
ask-grok is an MCP server published in the GitHub repository Lykhoyda/ask-llm (18 stars, last pushed yesterday), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-14.
Other mcp servers, from other repositories
promptheus
AI-powered prompt engineering CLI tool. Runs locally from the promptheus Python package. Needs 8 environment variables to run.
polyprompt
MCP server "polyprompt" as configured in DisSa12/polyprompt. Launched with polyprompt mcp.
llm-router-mcp
MCP server that routes prompts across Claude, Gemini, and GPT-4o to minimise token cost. Runs locally from the llm-router-mcp npm package.
mcp
Detect prompt injection, jailbreaks, and code injection in untrusted text before it reaches an LLM. Runs locally from the @safeprompt.dev/mcp npm package. Needs 3 environment variables to run.
compactprompt
Easy-to-use prompt & data compression for LLM workflows. Runs locally from the compactprompt Python package.
promptest-mcp
MCP server "promptest-mcp" as configured in cortexresearch/promptest-mcp. Runs locally from the promptest-mcp npm package.