What is oss-repo-check CLAUDE.md?

Project instructions for maintaining an open-source repository and its quaid-scanner tool, including file placement, commit rules, testing, and TypeScript conventions.

Use them when adding features, documentation, or tests to quaid-scanner, organizing files, preparing commits, and checking coverage and code quality.

They give the agent repository-specific rules, such as where documentation belongs and which tests and quality checks must pass before changes are accepted.

How AINative-Studio/oss-repo-check configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to AINative-Studio/oss-repo-check. 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/AINative-Studio/oss-repo-check/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/AINative-Studio/oss-repo-check

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/ainative-studio/oss-repo-check/claude-md/github.svg)](https://agentmods.dev/instructions/ainative-studio/oss-repo-check/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/ainative-studio/oss-repo-check/claude-md"><img src="https://agentmods.dev/badge/instructions/ainative-studio/oss-repo-check/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/ainative-studio/oss-repo-check/claude-md"><img src="https://agentmods.dev/badge/instructions/ainative-studio/oss-repo-check/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,091 This file is loaded in full into every session.

When invoked 1,091 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 original No closer match found 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.

Model	Per session	Once invoked
Fable 5.1	$0.01091	$0.01091
Opus 5	$0.00545	$0.00545
Sonnet 5	$0.00218	$0.00218
Haiku 4.5	$0.00109	$0.00109

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

Security

Grade A, and why

oss-repo-check 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.

CLAUDE.md · 123 lines

How it starts

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

quaid-scanner - Project Memory

Last Updated: 2026-05-04 Project Root: /Users/karstenwade/Projects/quaid-scanner

Critical Rules

1. Git Commits

Zero tolerance for AI attribution
No "Claude", "Anthropic", "Generated with", "Co-Authored-By" in commits
commit-msg hook enforces this

2. File Placement

Docs → docs/{category}/
No root .md files (except README.md and CLAUDE.md)
Content drafts (blog, social, release marketing) → docs/content/v{version}/{type}/
- Draft here first; feed into blog-sources pipeline only at publish time
- Applies to all content: blog posts, social threads, release notes marketing copy

3. Testing (MANDATORY)

80%+ coverage required
All features tested
TDD approach preferred
npm test runs vitest

4. Code Quality

TypeScript strict mode, type hints on all functions
Docstrings for public methods
Clean, readable code

Agent-First Toolchain Intent

quaid-scanner is designed to be operated by an agent, not just a human. The full value of the tool only emerges when an agent drives the workflow end-to-end:

Scanning — run quaid-scanner against one or many repos, capture JSON output
Analysis — parse findings, group by category, identify cross-portfolio patterns
Reporting — fill docs/scans/portfolio-report-template.md from scan JSON; the template contains inline agent instructions for every section
Backlog generation — derive user stories from findings using the story template bank at the bottom of the report template
Issue creation — open GitHub issues from the backlog stories, one issue per story

When working on this toolchain, keep this intent in mind:

JSON is the primary output format — markdown is secondary
--quiet --format json is the canonical agent invocation
The report template is written for an agent reader; comments are instructions, not decoration
Scanner findings should always include a suggestion field — that's what feeds the story want clause
Scans of large portfolios should run in parallel (background bash jobs or parallel agents)

Read the full file on GitHub · 123 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.

9d ago First seen · 123 lines · 1,091 tokens per session scan A a8ca5f0ff404

Subscribe to this mod's changes

oss-repo-check CLAUDE.md is an instructions file published in the GitHub repository AINative-Studio/oss-repo-check (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 1,091 tokens to every session, about $0.0055 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.

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

oss-repo-check: Instructions file for Claude Code