Coding-Agent-Guidelines-Radiotherapy AGENTS.md

Coding-Agent-Guidelines-Radiotherapy AGENTS.md is an instructions file for Codex, OpenCode from MustafaKadhim/Coding-Agent-Guidelines-Radiotherapy. It costs 2,236 tokens per session, scanned A, original, MIT.

Repository instructions for coding work in a medical-physics and radiotherapy research project. They give an AI coding assistant guidance on thinking through requests, making simple changes, and handling scientific or clinical ambiguity carefully.

In plain words
What is it for?
Use them when editing or reviewing Python, PyTorch, medical-imaging, deep-learning, evaluation, or radiotherapy research code in that project.
Why use it?
They provide project-specific expectations so code changes, experiments, data processing, and model work fit the repository and avoid unsafe or statistically weak assumptions.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Codex.

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 instructions/mustafakadhim/coding-agent-guidelines-radiotherapy/agents-md
Clone the repo
git clone --depth 1 https://github.com/MustafaKadhim/Coding-Agent-Guidelines-Radiotherapy

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for Coding-Agent-Guidelines-Radiotherapy AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/mustafakadhim/coding-agent-guidelines-radiotherapy/agents-md.svg)](https://agentmods.dev/instructions/mustafakadhim/coding-agent-guidelines-radiotherapy/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/mustafakadhim/coding-agent-guidelines-radiotherapy/agents-md"><img src="https://agentmods.dev/badge/instructions/mustafakadhim/coding-agent-guidelines-radiotherapy/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,236 This file is loaded in full into every session.
When invoked 2,236 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original 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.1 $0.02236 $0.02236
Opus 5 $0.01118 $0.01118
Sonnet 5 $0.00447 $0.00447
Haiku 4.5 $0.00224 $0.00224

Measured 6d ago against content hash 46a75eae45fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

Coding-Agent-Guidelines-Radiotherapy AGENTS.md 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 6d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 321 lines

How it starts

The opening of the file, as written. The whole thing — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Codex Coding Instructions

(feel free to change based on your background!)

These instructions apply when helping me with code, debugging, experiments, data processing, model development, evaluation, or scientific-computing workflows.

I'm a medical physicist and PhD student in external radiotherapy working with deep learning, medical imaging, and radiotherapy research. Assume strong familiarity with Python, PyTorch (PyTorch Lightning), MONAI, medical image analysis, radiotherapy concepts, statistics, and model evaluation.


1. Operating Principles

Think Before Coding

Before implementation, clarify the task enough to avoid wrong work.

  • State important assumptions before acting.
  • If ambiguity affects correctness, safety, data handling, APIs, experiment validity, or clinical interpretation, ask.
  • If ambiguity is minor and reversible, make a conservative assumption and state it.
  • If multiple valid interpretations exist, briefly present them and recommend the simplest.
  • Push back when the requested approach is likely overcomplicated, unsafe, statistically weak, or not aligned with the goal.

Simplicity First

Prefer the minimum correct solution.

  • Do not add features that were not requested.
  • Do not add abstractions for one-off code.
  • Do not add unnecessary configurability.
  • Do not rewrite working code just to make it prettier.
  • If the solution can be substantially shorter without losing clarity or robustness, simplify it.

Surgical Changes

When editing existing code:

  • Touch only files and lines required for the task.
  • Match the existing project style, naming, structure, and dependency patterns.
  • Do not refactor adjacent code unless it is required for the requested change.
  • Do not clean up unrelated dead code unless asked.
  • Remove imports, variables, functions, files, or comments made unused by your own changes.
  • Mention unrelated issues separately instead of silently changing them.

Every changed line should trace directly to the user's request.

Read the full file on GitHub · 321 lines

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. 6d ago First seen · 321 lines · 2,236 tokens per session scan A 46a75eae45fe

Subscribe to this mod's changes

Coding-Agent-Guidelines-Radiotherapy AGENTS.md is an instructions file published in the GitHub repository MustafaKadhim/Coding-Agent-Guidelines-Radiotherapy (11 stars, last pushed 4mo ago), licensed MIT. It adds 2,236 tokens to every session, about $0.0112 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.

Related

Other instructions, from other repositories