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.
npx agentmods add rules/rishapgandhi/python-skills/python-coregit clone --depth 1 https://github.com/rishapgandhi/python-skillsWhat 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 | $0.00158 | $0.00158 |
| Opus 5 | $0.00079 | $0.00079 |
| Sonnet 5 | $0.00032 | $0.00032 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
python-core 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.
What it actually says
Python Core Rules
- 4 spaces indentation, no tabs
- Full type annotations on all function signatures
- Docstrings on all public functions/classes (Google style)
- No hardcoded secrets — use pydantic-settings
- structlog for logging — never print()
- Never bare
except:— catch specific exceptions - Never use mutable default arguments
- Monetary values: Decimal, never float
- Prefer
X | NoneoverOptional[X] - Use
from __future__ import annotationsfor forward refs - Layer discipline: API → Service → Repository → Model
Reference: skills/common/code-style.md
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.
- yesterday First seen · 22 lines · 158 tokens per session scan A 9982b2912ee1
python-core is a cursor rule published in the GitHub repository rishapgandhi/python-skills (4 stars, last pushed 3mo ago), licensed MIT. It adds 158 tokens to every session, about $0.0008 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 cursor rules, from other repositories
general
Cursor rule "general" from maxgfr/conforme, covering claude.md, project overview, build & test, architecture and keeping docs in sync.
checklist
Before making ANY changes or implementing ANY new features.
nextjs-patterns
// ✅ Correct: Default to Server Components export default async function Page({ params }) { const data = await getData(); return ; }.
testing
testing.
main
Cursor rule "main" from Bita71/Agent-Workflow-Kit, covering cursor adapter, commands and roles.
task
Task execution rules for Glitch Payment Gateway engineering work — verification gates, plan node, self-improvement loop.