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.
git clone --depth 1 https://github.com/alwaysmeticulous/skillsWrote 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/rules/alwaysmeticulous/skills/no-private-repo-references)<a href="https://agentmods.dev/rules/alwaysmeticulous/skills/no-private-repo-references"><img src="https://agentmods.dev/badge/rules/alwaysmeticulous/skills/no-private-repo-references/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/rules/alwaysmeticulous/skills/no-private-repo-references"><img src="https://agentmods.dev/badge/rules/alwaysmeticulous/skills/no-private-repo-references.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.00315 | $0.00315 |
| Opus 5.5 | $0.00126 | $0.00126 |
| Sonnet 5.5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
no-private-repo-references 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 12d 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
No references to private repos
This repo (alwaysmeticulous/skills) is public. The repos it's developed alongside — most notably alwaysmeticulous/meticulous — are private. Never reference them in anything that ends up in this repo or on its GitHub pages:
- skill files, the README and other docs
- commit messages
- PR titles and descriptions, PR/review comments and replies
That rules out:
- private repo names, or phrases like "the meticulous repo" / "the main repo"
- links or
owner/repo#123references to private PRs, issues or commits - internal file paths, package names, services or tooling (e.g.
public_packages/…,webapp-backend) - internal processes, such as syncing these skills into another repo via
skills-lock.json
Describe changes in terms of what's publicly visible instead: the published CLI (@alwaysmeticulous/cli) and its commands and flags, the Meticulous MCP server and its tools, the web app, and the public docs. For example, write "the CLI now supports --prNumber", not "documents --prNumber (alwaysmeticulous/meticulous#14667)"; and "not in a released CLI yet", not "from PRs still open in the main repo".
References to this repo's own PRs and issues are fine.
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.
- 12d ago First seen · 24 lines · 315 tokens per session scan A 20043bf954ba
no-private-repo-references is a cursor rule published in the GitHub repository alwaysmeticulous/skills (10 stars, last pushed 2d ago), licensed ISC. It adds 315 tokens to every session, about $0.0013 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-06.
Other cursor rules, from other repositories
legal-advisor
Draft privacy policies, terms of service, disclaimers, and legal notices. Creates GDPR-compliant texts, cookie policies, and data processing agreements.
hatch3r-data-classification
Data classification standards covering PII handling, encryption, retention policies, and regulatory compliance.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.