ai-disk-doctor-integrations: Instructions file for Codex

AGENTS.md

ai-disk-doctor-integrations AGENTS.md is an instructions file for Codex, OpenCode from quzhiii/ai-disk-doctor-integrations. It costs 1,088 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for AI Disk Doctor Integrations, the layer connecting AI Disk Doctor to tools such as MCP, skills, and agents.

In plain words
What is it for?
Use them when changing or reviewing this integration repository, especially its adapters, compatibility rules, projections, or distribution work.
Why use it?
They clarify which repository owns each responsibility and require specific project documents to be read before work begins.

Instructions file for CodexOpenCode

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

This is quzhiii/ai-disk-doctor-integrations's own configuration. It tells Codex and OpenCode how to work on ai-disk-doctor-integrations itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-disk-doctor-integrations configures →

Reuse

Borrowing it

Nothing to install: this file belongs to quzhiii/ai-disk-doctor-integrations. 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/quzhiii/ai-disk-doctor-integrations/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/quzhiii/ai-disk-doctor-integrations

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 ai-disk-doctor-integrations AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/quzhiii/ai-disk-doctor-integrations/agents-md/github.svg)](https://agentmods.dev/instructions/quzhiii/ai-disk-doctor-integrations/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/quzhiii/ai-disk-doctor-integrations/agents-md"><img src="https://agentmods.dev/badge/instructions/quzhiii/ai-disk-doctor-integrations/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.

agentmods 80×15 button for ai-disk-doctor-integrations AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/quzhiii/ai-disk-doctor-integrations/agents-md"><img src="https://agentmods.dev/badge/instructions/quzhiii/ai-disk-doctor-integrations/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,088 This file is loaded in full into every session.
When invoked 1,088 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01088 $0.01088
Opus 5 $0.00544 $0.00544
Sonnet 5 $0.00218 $0.00218
Haiku 4.5 $0.00109 $0.00109

Measured 8d ago against content hash 2584ba36768a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

ai-disk-doctor-integrations 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 8d 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 · 138 lines

How it starts

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

Project Identity

AI Disk Doctor Integrations is the MCP, Skill, Agent adapter, and compatibility layer for AI Disk Doctor. It also owns bounded projections, Agent validation, and self-service Agent distribution.

It is not a scanner, cleaner, risk engine, policy engine, recovery engine, Desktop, or second Core implementation. The Core repository, quzhiii/ai-disk-doctor, is the execution and policy source of truth.

Repository Boundary

Integration owns:

  • MCP and Skill integration;
  • Agent adapters and compatibility contracts;
  • bounded, evidence-preserving projections;
  • Agent/client validation;
  • self-service Agent distribution.

Integration does not own scanner logic, cleanup semantics, risk classification, recoverability policy, filesystem mutation policy, or Desktop UX. Do not duplicate Core behavior in this repository.

Required Reading

At the start of every new Agent session, before substantive work, use the Read tool to read these files in order:

  1. docs/governance/MILESTONE_PROTOCOL.md
  2. docs/milestones/CURRENT.md
  3. The milestone contract named by CURRENT.md

Do not assume Markdown paths are automatically expanded or loaded. Actually read each file with the Read tool. Then audit the current repository, branch, HEAD, working tree, relevant code, docs, tests, and workflows.

Runtime / Product Truth

Use this order to determine what the product and runtime currently are:

  1. Current repository code and public contracts
  2. Current accepted runtime and product documentation
  3. Current accepted validation evidence
  4. Historical decisions and validation records
  5. Chat assumptions

Code and public contracts decide current reality. Historical or archived material must not override it. Label historical evidence as historical and do not present it as runtime behavior.

Execution Authority

Use this order to determine what the Agent is authorized to do in the current milestone:

  1. Frozen current milestone contract
  2. Repo-level governance in AGENTS.md and docs/governance/MILESTONE_PROTOCOL.md
  3. Accepted product and runtime documentation as supporting context
  4. Chat assumptions

Read the full file on GitHub · 138 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. 8d ago First seen · 138 lines · 1,088 tokens per session scan A 2584ba36768a

Subscribe to this mod's changes

ai-disk-doctor-integrations AGENTS.md is an instructions file published in the GitHub repository quzhiii/ai-disk-doctor-integrations (0 stars, last pushed 8d ago), licensed Apache-2.0. It adds 1,088 tokens to every session, about $0.0054 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.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 3,735 tokens