What is no-private-repo-refs?

A repository rule that prevents links, names, and references to private GitHub repositories from appearing in public project material. Public project material includes commits, pull requests, comments, documentation, and logs.

It is for checking commits, pull requests, documentation, branches, and other public artifacts for private-repository references.

It reduces the risk of exposing internal repository names or tracking details in a publicly readable codebase. It explains that public issue references or no reference should be used instead.

no-private-repo-refs — Cursor rule for Cursor by bayesimpact

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/bayesimpact/bayes-platform

Made for: Cursor.

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/rules/bayesimpact/bayes-platform/no-private-repo-refs/github.svg)](https://agentmods.dev/rules/bayesimpact/bayes-platform/no-private-repo-refs)

Your own site

<a href="https://agentmods.dev/rules/bayesimpact/bayes-platform/no-private-repo-refs"><img src="https://agentmods.dev/badge/rules/bayesimpact/bayes-platform/no-private-repo-refs/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/rules/bayesimpact/bayes-platform/no-private-repo-refs"><img src="https://agentmods.dev/badge/rules/bayesimpact/bayes-platform/no-private-repo-refs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 426 This file is loaded in full into every session.

When invoked 426 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.00426	$0.00426
Opus 5.5	$0.00170	$0.00170
Sonnet 5.5	$0.00085	$0.00085
Haiku 4.5	$0.00043	$0.00043

Measured 28d ago against content hash 54c30c2cbe73, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

no-private-repo-refs 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 28d 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.

.cursor/rules/no-private-repo-refs.mdc · 39 lines

What it actually says

No private-repo references in this public repo

bayesimpact/bayes-platform is public. Anything written here is world-readable: commits, PR titles/bodies, comments, code, docs, changelogs, branch names that spell a private repo, CI logs you paste into PRs.

Forbidden in this repository

Never put any of the following into commits, PRs, comments, docs, code, or changelogs:

Links or names of private GitHub repos (especially bayesimpact/internal-issues)
Closes / Fixes / Refs / Part of trailers that point at a private repo issue (e.g. Closes bayesimpact/internal-issues#137, Refs: bayesimpact/internal-issues#137)
Internal-only URLs, tickets, or tracker IDs that only resolve inside a private org repo

Tracking a private security/internal issue is fine in chat with the user. Do not mirror that reference into the public git history or GitHub UI.

What to write instead

Describe the change on its own (no private issue link).
If a public bayes-platform issue exists, link that (Closes #1234).
If work was driven by a private issue only, omit the reference entirely.

# ❌ BAD — leaks a private tracker into the public repo
Closes bayesimpact/internal-issues#137
Refs: bayesimpact/internal-issues#137

# ✅ GOOD — no private tracker
# (no Closes/Refs line, or Closes #<public bayes-platform issue>)

Before every commit and `gh pr create` / `gh pr edit`

Scan the message/body for internal-issues, other private repo slugs, and bayesimpact/ links that are not bayesimpact/bayes-platform. Remove them before committing or publishing.

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.

28d ago First seen · 39 lines · 426 tokens per session scan A 54c30c2cbe73

Subscribe to this mod's changes

no-private-repo-refs is a cursor rule published in the GitHub repository bayesimpact/bayes-platform (23 stars, last pushed yesterday), licensed MIT. It adds 426 tokens to every session, about $0.0017 per session on Opus 5.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-10-09.