Borrowing it
Nothing to install: this file belongs to kirandevihosur74/mcp-sentinel. 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/kirandevihosur74/mcp-sentinel/main/CLAUDE.mdgit clone --depth 1 https://github.com/kirandevihosur74/mcp-sentinelWrote 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/kirandevihosur74/mcp-sentinel/claude-md)<a href="https://agentmods.dev/instructions/kirandevihosur74/mcp-sentinel/claude-md"><img src="https://agentmods.dev/badge/instructions/kirandevihosur74/mcp-sentinel/claude-md/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/instructions/kirandevihosur74/mcp-sentinel/claude-md"><img src="https://agentmods.dev/badge/instructions/kirandevihosur74/mcp-sentinel/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.01016 | $0.01016 |
| Opus 5 | $0.00508 | $0.00508 |
| Sonnet 5 | $0.00203 | $0.00203 |
| Haiku 4.5 | $0.00102 | $0.00102 |
Grade A, and why
mcp-sentinel 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 11d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project rules for the coding assistant working in mcp-sentinel. Read README.md first for what we are building.
What this is
An agent on TrueForge that audits MCP servers: scrape registries (Bright Data), inspect each server in a Daytona sandbox (subagents), judge, then open approval-gated PRs against allowlist.json. See README.md for the four stages and the demo script.
Rules
- TypeScript everywhere. Node 22+.
- The harness does the loop, tool calls, subagents, sandbox, approvals and sessions. Do not reimplement any of that. If something feels like plumbing, check whether TrueForge already does it.
- Third-party MCP server code runs only inside the Daytona sandbox. Never
npm installor execute a server under audit on the host. - Every action with external effect (PR, abuse report) goes through a TrueForge approval. No exceptions, including in tests.
- Work on branches. Open a PR for every change. Qodo reviews it. Fix High findings before merge.
- Commit messages are imperative ("Add canary check", not "Added canary check").
- Keep files small and single-purpose. A hackathon repo that reads like real software is the Qodo track.
Bright Data scraper configuration
All web data goes through Bright Data. Never use plain fetch against a registry.
CLI is installed and authenticated (bdata config must succeed). Zone: cli_unlocker.
Registries
| Registry | Listing URL pattern | Fields we need |
|---|---|---|
| npm | https://www.npmjs.com/package/<name> |
version, published date, maintainers, weekly downloads, repo URL |
| Smithery | https://smithery.ai/server/<owner>/<name> |
version, tools list (name + description), repo URL, install count |
| Glama | https://glama.ai/mcp/servers/<id> |
tools list, repo URL, last updated |
| mcp.so | https://mcp.so/server/<name> |
description, repo URL, tags |
Start with npm and Smithery. Add the others only if both are solid.
Collectors (Scraper Studio)
Create one collector per registry from a plain-English description, then record the collector_id here so it is reused and version-controlled:
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.
- 11d ago First seen · 95 lines · 1,016 tokens per session scan A 7e3bfb3242c0
mcp-sentinel CLAUDE.md is an instructions file published in the GitHub repository kirandevihosur74/mcp-sentinel (0 stars, last pushed 13d ago), licensed MIT. It adds 1,016 tokens to every session, about $0.0051 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
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.
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.
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).
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).