Borrowing it
Nothing to install: this file belongs to MaxPopov/wikijs-mcp-google-auth. 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/MaxPopov/wikijs-mcp-google-auth/dev/CLAUDE.mdgit clone --depth 1 https://github.com/MaxPopov/wikijs-mcp-google-authWrote 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/maxpopov/wikijs-mcp-google-auth/claude-md)<a href="https://agentmods.dev/instructions/maxpopov/wikijs-mcp-google-auth/claude-md"><img src="https://agentmods.dev/badge/instructions/maxpopov/wikijs-mcp-google-auth/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/maxpopov/wikijs-mcp-google-auth/claude-md"><img src="https://agentmods.dev/badge/instructions/maxpopov/wikijs-mcp-google-auth/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.02045 | $0.02045 |
| Opus 5 | $0.01022 | $0.01022 |
| Sonnet 5 | $0.00409 | $0.00409 |
| Haiku 4.5 | $0.00204 | $0.00204 |
Grade A, and why
wikijs-mcp-google-auth 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project rules for AI assistants
Guidance for Claude Code / AI agents working in this repo. Keep it accurate — if the release workflow or branching model changes, update this file in the same PR.
Branching model
dev— integration branch. All work lands here first, via PR.main— release branch. It only ever receives merges fromdev. Every push tomainis a potential release (see below).- Feature/fix branches → PR into
dev. Never open day-to-day work PRs straight intomain; the one exception is a release-enabling hotfix to the release workflow itself. - The repo has a ruleset requiring a PR + approving review to merge. Merges are done with admin bypass ("Bypass rules and merge") or via the API with an admin token.
- A merged branch is finished. Never stack new commits on already-merged
history — restart the working branch from the latest base
(
git checkout -B <branch> origin/dev).
Commit messages: Conventional Commits are load-bearing
Release versions are computed FROM COMMIT MESSAGES. A commit that does not follow the convention is invisible to the release tooling, so a release that consists only of such commits never gets proposed.
Prefix every commit subject:
| Prefix | Effect on the next version |
|---|---|
fix: |
patch (0.2.0 -> 0.2.1) |
feat: |
minor (0.2.0 -> 0.3.0) |
feat!: / fix!:, or a BREAKING CHANGE: footer |
major (0.2.0 -> 1.0.0) |
chore:, docs:, test:, refactor:, ci:, build: |
none — shipped, but does not by itself trigger a release |
The prefix must be on the COMMIT, not only on the PR title: this repo merges feature branches with merge commits, so the individual commits are what the tooling reads. (If a PR is squash-merged instead, the PR title becomes the commit subject and it is the title that must carry the prefix.)
How releases work (READ THIS BEFORE MERGING TO main)
Releases are automatic and the version is never edited by hand. Two workflows split the job:
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.
- 8d ago First seen · 147 lines · 2,045 tokens per session scan A 3a4e48416bdb
wikijs-mcp-google-auth CLAUDE.md is an instructions file published in the GitHub repository MaxPopov/wikijs-mcp-google-auth (0 stars, last pushed 13d ago), licensed Apache-2.0. It adds 2,045 tokens to every session, about $0.0102 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.
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.