diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 4132c1a42cb..6b0e38833f4 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -1,10 +1,31 @@
 ## What
 _This section describes what this PR is about. It should be a clear and concise description concerning what this PR is for, why this PR is needed, and why it should be accepted._
+
 _Linking an issue can be used alternatively to writing a description._
 
+
 ## Implementation Details
 _Any implementations in this PR that should be carefully looked over, or that could/should have alternate solutions proposed._
 
+### AI Usage 
+_The usage of AI tools requires honest disclosure, please refer to our [AI Policy](https://github.com/GregTechCEu/GregTech-Modern/blob/1.20.1/AI_POLICY.md.)._
+
+The purpose of this section is to not guilt trip users who engage with these tools but to give us a better understanding of how they were used as well to what extent.
+Users who contribute AI written code are held responsible for the quality of the code as well as understanding the implemented code written by these tools.
+
+**All machine code MUST be reviewed by the pull request submitter before opening. **
+
+- [ ] No AI driven tools were used for this pull request.
+- [ ] Yes AI driven tools were used for this pull request.
+
+_If you answered no and it is discovered the pull request in question used AI tooling, users will be restricted from submitting future pull requests_
+
+_If you answered yes, please fill out the following information_
+#### Agent Used
+_Example: ClaudeCode Opus 4.7, GPT-5.3-Codex, etc_
+#### Agent Usage Description
+_The extent the relevant tools were used for this PR, be concise and clear with what it was used for. Machine code coverage is not inherently bad, but users must review all machine code personally before submitting a pull request._
+  
 ## Outcome
 _A short description of what this PR added/fixed/changed/removed._
 _For correct linking of issues please use any of the Closes/Fixes/Resolves keywords. Example: When a PR is fixing a bug use "Fixes: #number-of-bug"_
@@ -18,4 +39,4 @@ _This section is for screenshots to demonstrate any GUI or rendering changes, or
 ## Potential Compatibility Issues
 _This section is for defining possible compatibility issues. It must be used when there are API changes, item/block/material/machine changes, or recipe changes._
 
-**Please fill in as much useful information as possible. Also, please remove all unused sections, including this and the other explanations.**
\ No newline at end of file
+**Please fill in as much useful information as possible. Also, please remove all unused sections, including this and the other explanations.**