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/burakcanpolat/med-guide/medgemmagit clone --depth 1 https://github.com/burakcanpolat/med-guideWrote 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/burakcanpolat/med-guide/medgemma)<a href="https://agentmods.dev/rules/burakcanpolat/med-guide/medgemma"><img src="https://agentmods.dev/badge/rules/burakcanpolat/med-guide/medgemma.svg" alt="Measured on agentmods" 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 | $0.02357 | $0.02357 |
| Opus 5 | $0.01179 | $0.01179 |
| Sonnet 5 | $0.00471 | $0.00471 |
| Haiku 4.5 | $0.00236 | $0.00236 |
Grade A, and why
medgemma 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Med-Guide
Medical image analysis and general medical assistant project. Explain everything in a way that an ordinary person with no medical knowledge can understand.
Language Preference
At the start of every conversation, check reports/user_config.md.
- If the file exists and contains a
language:field → use that language for all interactions. - If the file does not exist:
- Ask:
🌐 Please choose your language / Lütfen dilinizi seçin: 1. 🇬🇧 English 2. 🇹🇷 Türkçe - Save the choice to
reports/user_config.md:
(orlanguage: enlanguage: tr) - Confirm in the chosen language and proceed.
- Ask:
All subsequent communication, reports, and analysis output MUST be in the user's chosen language.
First-Run Check
After setting the language, check if the .env file exists. If it doesn't:
- Tell the user (in their chosen language): "Welcome! This looks like your first time. Shall we set things up together?"
- If they agree, read
skills/setup-skill.mdand start the setup wizard - Do not perform any analysis until setup is complete
If the user says "setup", "install", "kurulum", "get started", "start setup" → read and apply skills/setup-skill.md.
If the user says "help", "yardım" → read the HELP COMMAND section from .agents/skills/medgemma-setup/SKILL.md.
If the user says "test", "connection test", "bağlantı testi" → run a test analysis with a sample image.
If the user says "settings", "ayarlar" → show the contents of .env.
Skill Routing
| User says / provides | What to do |
|---|---|
| "setup", "install", "kurulum", "get started" | Read and apply skills/setup-skill.md |
| Medical images (X-ray, CT, MRI, DICOM files) | Follow Radiology Report Format below |
.dcm file, ZIP with DICOM, "analyze this scan" |
Follow Radiology Report Format below |
| Lab results, blood work, medications, symptoms | Follow Medical Assistant Format below |
| Drug interactions, medical report text | Follow Medical Assistant Format below |
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.
- 4d ago First seen · 223 lines · 2,357 tokens per session scan A acd0d592f9a6
medgemma is a cursor rule published in the GitHub repository burakcanpolat/med-guide (2 stars, last pushed 5mo ago), licensed MIT. It adds 2,357 tokens to every session, about $0.0118 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
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.