Borrowing it
Nothing to install: this file belongs to Lipdog/fossick-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Lipdog/fossick-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/Lipdog/fossick-mcpWrote 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/lipdog/fossick-mcp/claude-md)<a href="https://agentmods.dev/instructions/lipdog/fossick-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/lipdog/fossick-mcp/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.1 | $0.02234 | $0.02234 |
| Opus 5 | $0.01117 | $0.01117 |
| Sonnet 5 | $0.00447 | $0.00447 |
| Haiku 4.5 | $0.00223 | $0.00223 |
Grade A, and why
fossick-mcp 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 7d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project instructions for AI coding agents working on fossick-mcp. Covers what the project is, how it's organized, and the recipes for common tasks.
Table of contents
- What fossick is
- Stack
- Repository layout
- Key patterns
- Tools
- Hints system
- Adding a new tool
- Tests
- Rate limits
- Conventions
What fossick is
Discovery-focused MCP server for finding and evaluating new libraries, frameworks, and packages to adopt in new projects. Seven tools covering the "starting a project, need to pick the right dependency" workflow, spanning GitHub (200M+ repos), PyPI, and npm.
NOT for code archaeology — git history, blame, PR tracking, version diffing. Reach for git / gh CLI via Bash instead.
The name comes from the Australian/NZ verb fossick — "to prospect or rummage for gems" — which is what the tool does: sift 200M+ repos down to the handful worth evaluating.
Stack
- Python 3.11+, pinned via
.python-version uvfor package management and builds- FastMCP (
mcp >= 1.26) with stdio transport httpxfor async GitHub API calls- Pydantic for settings
tree-sitterfor AST-based symbol search
Repository layout
src/fossick/
server.py — FastMCP instance, instructions, lifespan, tool imports
github_client.py — Async httpx client, auth, rate limits, retry
cache.py — In-memory TTL cache with LRU eviction
hints.py — Rule-based next-step suggestion engine
tools/ — One file per tool
tools/_common.py — Shared helpers (split_repo, http_error_to_tool_error)
tools/_tree_sitter.py — AST queries for find_symbol
tests/
unit/ — No network. Classifier branches, cache, hints, etc.
integration/ — Live, pinned to modelcontextprotocol/[email protected]
test_registration.py — Schema + registration smoke for all 7 tools
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.
- 7d ago First seen · 147 lines · 2,234 tokens per session scan A bcee5c0cfe62
fossick-mcp CLAUDE.md is an instructions file published in the GitHub repository Lipdog/fossick-mcp (3 stars, last pushed 4mo ago), licensed MIT. It adds 2,234 tokens to every session, about $0.0112 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
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.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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).
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.