701-github

Rules for GitHub code and configuration, covering organizational and workflow practices.

In plain words
What is it for?
Use them when creating or checking GitHub code and configuration, such as repository workflows or organization settings. The exact rules are not provided.
Why use it?
They help avoid maintainability, security, and efficiency problems in GitHub-related work.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/davenicoll/cursor-rules/701-github
Clone the repo
git clone --depth 1 https://github.com/davenicoll/cursor-rules

Made for: Cursor.

Per session 1,177 This file is loaded in full into every session.
When invoked 1,177 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.

ModelPer sessionOnce invoked
Fable 5 $0.01177 $0.01177
Opus 5 $0.00589 $0.00589
Sonnet 5 $0.00235 $0.00235
Haiku 4.5 $0.00118 $0.00118

Measured yesterday against content hash d69098fc460b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

701-github 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 yesterday.

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/701-github.mdc · 161 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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.

  1. yesterday First seen · 161 lines · 1,177 tokens per session scan A d69098fc460b

Subscribe to this mod's changes

701-github is a cursor rule published in the GitHub repository davenicoll/cursor-rules (12 stars, last pushed 1y ago), with no licence file. It adds 1,177 tokens to every session, about $0.0059 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-30.