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/sandraschi/gitee-mcp/cursorrulesgit clone --depth 1 https://github.com/sandraschi/gitee-mcpWhat 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.00250 | $0.00250 |
| Opus 5 | $0.00125 | $0.00125 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
cursorrules 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
Cursor rules for gitee-mcp
- Backend: FastMCP 3.4.4+, portmanteau tools,
uv run pythononly - Never fake data: anonymous repo search -> auth_required error
- Radar uses real live commits/stars; Gitee trending is unscrapable
just cibefore merge; ASCII-only scripts; no em dashes anywhere- One .env at repo root; secrets never in code
- GITEE_TOKEN unlocks the search tier (free token, no CC)
Session Context (Gitee MCP)
Bridge to Gitee (gitee.com), China's largest Chinese-language code hosting platform: live activity radar, repo intel, user/repo search and zh->en translation via your local LLM.
Before starting work:
- Check what is humming: gitee_explore(operation="humming", limit=10)
- Check status/tier: show_gitee_status_card() or gitee_help()
At end of work, save insights:
- Offer a watchlist of interesting repos you found (radar + repo commits)
- Respect the anonymous budget (~60 req/hour) - cache-aware, small limits
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 · 23 lines · 250 tokens per session scan A 8d51c71cd68e
cursorrules is a cursor rule published in the GitHub repository sandraschi/gitee-mcp (1 stars, last pushed 13d ago), licensed MIT. It adds 250 tokens to every session, about $0.0013 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
stock-data
Stock data domain (TW/US markets, FinMind, Massive, ticker insights, charts, translations). Auto-attached when editing stock-related code.
python
You are an expert in Python, FastAPI, and scalable API development.
uv
Use this rule when configuring or debugging uv environments, resolving dependency conflicts, or managing pyproject.toml entries.
fastapi-mcp-development-rules
당신은 FastAPI와 MCP(Model Context Protocol)를 활용한 프로덕션 수준의 API 서버를 개발하는 시니어 백엔드 개발자입니다. 다음 원칙들을 반드시 준수하여 코드를 작성하고 검토해야 합니다.
analytics-consent-onboarding
PostHog analytics, GDPR cookie consent, and onboarding tour usage.
internationalization
Cursor rule "internationalization" from dtyq/magic, covering internationalization (i18n) rules, 国际化基本规范, 1. 文件结构, 2. 命名空间规范 and 3. 组件中使用国际化.