Borrowing it
Nothing to install: this file belongs to acartag7/mcp-sso. 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/acartag7/mcp-sso/main/CLAUDE.mdgit clone --depth 1 https://github.com/acartag7/mcp-ssoWrote 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/acartag7/mcp-sso/claude-md)<a href="https://agentmods.dev/instructions/acartag7/mcp-sso/claude-md"><img src="https://agentmods.dev/badge/instructions/acartag7/mcp-sso/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/acartag7/mcp-sso/claude-md"><img src="https://agentmods.dev/badge/instructions/acartag7/mcp-sso/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.00420 | $0.00420 |
| Opus 5 | $0.00210 | $0.00210 |
| Sonnet 5 | $0.00084 | $0.00084 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
mcp-sso 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 9d 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.
What it actually says
@AGENTS.md
Claude Code session notes (mcp-sso)
AGENTS.md is the canonical source for this repo's rules, structure, commands,
invariants, and always-check list. This file keeps only context that is
specific to Claude Code sessions here and does not belong in the portable
AGENTS.md.
Build/extraction context (lives in Claude memory, not in the repo)
- The build/extraction plan is not kept in this repo (no handoff artifacts in repos — repo docs are durable-only). It lives in this project's Claude memory and in session prompts from the owner.
- Extraction source is
~/project/smart-fetch(Captatum) — read-only reference. Never copy deployment-specific details (hostnames, infra) or anysecurity-audit*document into this repo.
Repository quality rules
The canonical rules live in AGENTS.md, which this file includes
via @AGENTS.md. In short: keep the 16 manifest-frozen acceptance tests and all
five active phases intact; keep freeze-hash, mixed-diff, and
stage-artifact active; define product and security contracts before new trust
boundaries; fail closed with allowlists; and run the existing repository gates.
Sweep all adapters, stores, examples, and mutable-state exit paths for sibling
defects. Never weaken checks or push directly to protected branches. Use
conventional commits with the required Spec: <path> trailer, and prove each
regression test fails without its fix. Codex Reviewer must review the exact
final PR head, and every review object and inline thread must be read before
merge. After more than two unsuccessful review cycles, split or redesign the
PR.
Local review before Codex is class-closure-review, not a prose “sibling sweep.” Empty matrix cell = do not push.
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.
- 9d ago First seen · 38 lines · 420 tokens per session scan A ffbfe1223425
mcp-sso CLAUDE.md is an instructions file published in the GitHub repository acartag7/mcp-sso (8 stars, last pushed yesterday), licensed MIT. It adds 420 tokens to every session, about $0.0021 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
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).
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).
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.
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.