ac-infinity-mcp: Instructions file for Claude Code

CLAUDE.md

ac-infinity-mcp CLAUDE.md is an instructions file for Claude Code from RohanSan1/ac-infinity-mcp. It costs 4,484 tokens per session, scanned A, a copy of ac-infinity-mcp CLAUDE.md, MIT.

A set of contribution rules for a GitHub project, the platform used to host and review code. It requires feature branches, separate pull requests, staged checks, draft reviews, and explicit permission before merging.

In plain words
What is it for?
Use it to guide issue handling, pull-request creation, CI verification, branch checks, manual testing, and merge approval.
Why use it?
It prevents unreviewed changes from reaching the main branch and makes issue and pull-request work follow a fixed process.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions subagents.

This is RohanSan1/ac-infinity-mcp's own configuration. It tells Claude Code how to work on ac-infinity-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ac-infinity-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to RohanSan1/ac-infinity-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.

Copy the file
curl -O https://raw.githubusercontent.com/RohanSan1/ac-infinity-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/RohanSan1/ac-infinity-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for ac-infinity-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/rohansan1/ac-infinity-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/rohansan1/ac-infinity-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/rohansan1/ac-infinity-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/rohansan1/ac-infinity-mcp/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.

agentmods 80×15 button for ac-infinity-mcp CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/rohansan1/ac-infinity-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/rohansan1/ac-infinity-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 4,484 This file is loaded in full into every session.
When invoked 4,484 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 91% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.04484 $0.04484
Opus 5 $0.02242 $0.02242
Sonnet 5 $0.00897 $0.00897
Haiku 4.5 $0.00448 $0.00448

Measured 8d ago against content hash c726cdda235b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ac-infinity-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 8d 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.

Origin

This is a copy

91% identical to ac-infinity-mcp CLAUDE.md — 50 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.

CLAUDE.md · 385 lines

How it starts

The opening of the file, as written. The whole thing — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md — Contribution Protocol

This file is the authoritative source for how Claude agents contribute to this repo.


Contribution Rules

  • Never push directly to main. All work goes through feature branches + PRs.
  • Each phase = one PR. Phases are never bundled.
  • Every issue follows the 4-Stage Issue Workflow Protocol (see below).
  • No PR is raised until all four stages pass. Any stage failure restarts from Stage 1.
  • All PRs are created as drafts. Convert to "ready for review" only after Gate 5 (manual smoke test) is approved by the user. CI runs on draft PRs, so the test gate is not bypassed.
  • PRs are never merged without explicit user permission. After Gate 5 approval and all CI gates pass, present the status to the user and wait for them to say "merge" (or equivalent) before running gh pr merge.
  • Before declaring CI green or recommending merge, verify the PR's actual branch state: Run gh pr view <N> --json mergeStateStatus,headRefOid,headRefName and confirm mergeStateStatus is CLEAN (not BEHIND or DIRTY), and that headRefOid matches the local branch HEAD (git rev-parse HEAD). A PR that is BEHIND main must be rebased and re-pushed before the all-clear is given. Never report CI passing from a stale run — confirm the run SHA matches the current HEAD SHA.

GitHub Issue Hygiene

Every issue must have both a label and a milestone applied before a PR is raised against it. When creating a new issue, apply both immediately. When triaging unlabeled or un-milestoned issues, audit and update before beginning work.

Labels

Label When to apply
bug Incorrect behavior in an existing tool
enhancement New feature or capability
documentation Doc-only changes (API.md, README, CLAUDE.md, etc.)
security Security vulnerability or hardening
usability Response wording, field ordering, conflict UX, grower-readable output
api-discovery New API endpoints or fields discovered via network capture or reverse engineering

Read the full file on GitHub · 385 lines

Changes

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.

  1. 8d ago First seen · 385 lines · 4,484 tokens per session scan A c726cdda235b

Subscribe to this mod's changes

ac-infinity-mcp CLAUDE.md is an instructions file published in the GitHub repository RohanSan1/ac-infinity-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 4,484 tokens to every session, about $0.0224 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to ac-infinity-mcp CLAUDE.md, differing in 50 lines, and is treated as a copy.

Related

Other instructions, from other repositories

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 3,735 tokens