What is realme-c53-unlock-root AGENTS.md?

A guide for unlocking the bootloader and rooting certain Realme C53 phones, including phones using Unisoc, MediaTek, or Qualcomm chips. Rooting means gaining administrator-level access to Android.

Handling supported bootloader-unlock and root requests, choosing between KernelSU, Magisk, or both, and explaining when a device or requested operation is outside the project's scope.

It defines which devices and methods are supported, which tools users must provide, and which locks cannot be bypassed, reducing unsafe or misleading instructions.

How Gopartner/realme-c53-unlock-root configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to Gopartner/realme-c53-unlock-root. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Gopartner/realme-c53-unlock-root/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/Gopartner/realme-c53-unlock-root

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/gopartner/realme-c53-unlock-root/agents-md/github.svg)](https://agentmods.dev/instructions/gopartner/realme-c53-unlock-root/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/gopartner/realme-c53-unlock-root/agents-md"><img src="https://agentmods.dev/badge/instructions/gopartner/realme-c53-unlock-root/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/gopartner/realme-c53-unlock-root/agents-md"><img src="https://agentmods.dev/badge/instructions/gopartner/realme-c53-unlock-root/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 7,338 This file is loaded in full into every session.

When invoked 7,338 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.07338	$0.07338
Opus 5.5	$0.02935	$0.02935
Sonnet 5.5	$0.01468	$0.01468
Haiku 4.5	$0.00734	$0.00734

Measured 2mo ago against content hash b59cbc709142, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

realme-c53-unlock-root 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 2mo 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.

AGENTS.md · 692 lines

How it starts

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

AGENTS.md — Realme C53 / Multi-Chipset Unlock & Root Guide for AI

This file is the constitution for the AI agent. It defines:

What this project can do (and what it CANNOT do)
How to handle any user request — supported or not
Step-by-step workflows the AI must follow

Golden rule: Always stay within this project's scope. If a user asks for something outside scope, tell them honestly what this repo can/cannot do, and redirect if possible. Never pretend the repo supports something it doesn't.

Project Scope — What This Repo CAN Do

Category	Supported	Details
Bootloader unlock	✅ SPRD (Unisoc)	CVE-2022-38694, tools included
	⚠️ MediaTek	BROM mode, tools NOT included (user provides mtkclient)
	⚠️ Qualcomm	EDL / fastboot-oem, tools NOT included
	❌ Xiaomi Mi Unlock	Cannot bypass Xiaomi's waiting period
	❌ Huawei/Honor	Bootloader unlock permanently blocked
	❌ Samsung Knox	Cannot bypass Knox lock
Root method	✅ KernelSU LKM	Test-boot safety, requires matching vermagic
	✅ Magisk	Direct flash (no test-boot)
	✅ Hybrid (Magisk+KSU)	Recommended for RMX3760 — Magisk v27 for root, KSU module loaded via Magisk module
	✅ KernelSU Next LKM (GK12)	TESTED & WORKING — `u:r:ksu:s0`, fw `RMX3760export_15_H.01`
Init_boot	✅ Has partition	Stock init_boot contains real init + ramdisk
KSU-only	⚠️ Bug ksud init	KSU init binary fails on some setups; GK12 mode works (tested)
Build kernel module	✅ Via GitHub Actions	CI builds kernelsu.ko
	✅ Local build	Via kernel_ack_5.15/
Device support	✅ Any device with a TOML profile	See devices/ directory

How the AI Must Handle User Requests

Scenario A: User has a supported device (SPRD/Unisoc T6xx)

→ Follow AGENTS.md workflows normally. The user is in the right place.

Scenario B: User has a MediaTek device (Xiaomi, Realme MTK, etc.)

→ Guide them: "This repo has a MediaTek profile template and BROM unlock flow in CLI menu 5. You'll need mtkclient and MediaTek DA driver. Unlock via BROM may work if the device doesn't have locked BROM. Xiaomi MediaTek devices vary — some are unlockable, some aren't."

Read the full file on GitHub · 692 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.

2mo ago First seen · 692 lines · 7,338 tokens per session scan A b59cbc709142

Subscribe to this mod's changes

realme-c53-unlock-root AGENTS.md is an instructions file published in the GitHub repository Gopartner/realme-c53-unlock-root (3 stars, last pushed 3mo ago), licensed MIT. It adds 7,338 tokens to every session, about $0.0294 per session on Opus 5.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.

Mobile

realme-c53-unlock-root AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
realme-c53-unlock-root AGENTS.mdGopartner/realme-c53-unlock-root	Instructions file	3	3mo ago	MIT	A	7,338	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,649	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode ai-customization.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	1,907	GitHub Copilot

realme-c53-unlock-root: Instructions file for Codex