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 instructions/matthewgjohnson/ask-another/claude-mdgit clone --depth 1 https://github.com/matthewgjohnson/ask-anotherWrote 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/instructions/matthewgjohnson/ask-another/claude-md)<a href="https://agentmods.dev/instructions/matthewgjohnson/ask-another/claude-md"><img src="https://agentmods.dev/badge/instructions/matthewgjohnson/ask-another/claude-md.svg" alt="Measured on agentmods" height="20"></a>What 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.01552 | $0.01552 |
| Opus 5 | $0.00776 | $0.00776 |
| Sonnet 5 | $0.00310 | $0.00310 |
| Haiku 4.5 | $0.00155 | $0.00155 |
Grade A, and why
ask-another CLAUDE.md 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 4d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What This Is
An MCP (Model Context Protocol) server that lets Claude Desktop query other LLMs through a unified interface. It uses LiteLLM as the multi-provider backend and FastMCP for the server framework. Providers are configured via environment variables, and models are discovered dynamically via provider APIs.
Commands
uv sync # Install dependencies
PROVIDER_OPENAI="sk-test" uv run ask-another # Run the server locally
Release workflow — always pull after push
CI auto-bumps the patch version on every fix(...) commit pushed to main, then tags and builds the .mcpb. The bump appears as a chore: bump patch to X.Y.Z [skip ci] commit on origin/main that your local won't have. After any push that may have triggered the bump, git pull before doing more work — otherwise the repo's manifest.json/plugin.json will be one version behind reality and you'll build/install a stale bundle.
Tests can be run with:
uv run --with pytest python -m pytest tests/ -v
Architecture
The entire server lives in a single file: src/ask_another/server.py. It exposes these MCP tools:
search_families— discovers model families across configured providers, with optional substring searchsearch_models— finds specific model identifiers with optional substring search; enriches results with metadata (Elo, knowledge cutoff, context length, pricing, notes) from the annotations filecompletion— proxies a completion request to a specified LLM via LiteLLM, supports full model identifiers or favourite shorthand; tracks usage in the annotations fileannotate_models— adds or updates a personal note on a model; notes appear in search results and server instructionsrefresh_models— force re-scan of all providers and re-fetch benchmark data from LMArena arena-catalog (GitHub JSON) and LMArena metadata (HuggingFace CSV)feedback— collects usability issues from the LLM client into a JSONL log file (~/.ask-another-feedback.jsonlby default, configurable viaFEEDBACK_LOGenv var)start_research— starts a deep research task that runs in the background via a lifespan task group. Supports two paths: OpenRouter (Perplexity/OpenAI vialitellm.completion) and Gemini deep research (vialitellm.interactions.createwith polling). Blocks until results arrive or timeout, then returns results or a job handle. If interrupted (user hits escape), the research continues in the background.check_research— lists all research jobs as a markdown table, or retrieves full results for a specific job_idcancel_research— cancels a running research task by its job_idgenerate_image— generates an image from a text prompt. Automatically routes between two LiteLLM paths:litellm.image_generation()for dedicated image models (gpt-image-1, dall-e-3, imagen-4) andlitellm.completion()withmodalities=["image","text"]for native image-output models (Gemini Nano Banana family). Returns images inline via MCPImageContentand saves to disk.
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.
- 4d ago First seen · 97 lines · 1,552 tokens per session scan A 05353edafb33
ask-another CLAUDE.md is an instructions file published in the GitHub repository matthewgjohnson/ask-another (3 stars, last pushed 11d ago), licensed MIT. It adds 1,552 tokens to every session, about $0.0078 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.