Borrowing it
Nothing to install: this file belongs to lightbringer-patents/mcp-connector. 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/lightbringer-patents/mcp-connector/main/CLAUDE.mdgit clone --depth 1 https://github.com/lightbringer-patents/mcp-connectorWrote 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/lightbringer-patents/mcp-connector/claude-md)<a href="https://agentmods.dev/instructions/lightbringer-patents/mcp-connector/claude-md"><img src="https://agentmods.dev/badge/instructions/lightbringer-patents/mcp-connector/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/lightbringer-patents/mcp-connector/claude-md"><img src="https://agentmods.dev/badge/instructions/lightbringer-patents/mcp-connector/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.00293 | $0.00293 |
| Opus 5 | $0.00147 | $0.00147 |
| Sonnet 5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
mcp-connector 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 today.
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
100% identical to mcp-connector AGENTS.md — 0 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
Public repository instructions
This repository is public. Treat every GitHub write as publication, including files, commit messages, branch and tag names, PR titles and descriptions, comments, release notes, logs, screenshots, and packaged artifacts. Draft PRs are public too.
- Describe public product behavior using public product names, documented API/tool names, and public package versions.
- Do not add internal organization or repository names, private links or PR references, internal ticket IDs, codenames, backend release versions, deployment procedures, infrastructure details, credentials, or customer data.
- Keep internal evidence and cross-repository coordination in private records. Private records may link to public work; public content must not link back to private records. Do not copy internal release notes or agent transcripts here.
- Existing disclosures are not permission to repeat them. Do not include actual internal identifiers even as prohibited examples in public policy or checks.
- Before publishing, review the complete outgoing content and metadata, including every outgoing commit and generated artifact. CI and review after publication cannot prevent the initial disclosure.
- If disclosure is uncertain, omit the detail and resolve it privately with a maintainer. Report existing leaks privately; do not quote them in a public issue.
Read README.md for repository-specific work. Keep AGENTS.md and CLAUDE.md
equivalent when updating this policy.
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.
- today First seen · 25 lines · 293 tokens per session scan A 91c7bc8b97e0
mcp-connector CLAUDE.md is an instructions file published in the GitHub repository lightbringer-patents/mcp-connector (0 stars, last pushed yesterday), licensed MIT. It adds 293 tokens to every session, about $0.0015 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to mcp-connector AGENTS.md, differing in 0 lines, and is treated as a copy.
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.
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.
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).