Fix internal links: use eip-XXX.md convention for ERCs repo

Author: Brooks1003

ERCS/erc-8267.md

@@ -25,7 +25,7 @@ AI agents are proliferating across the blockchain ecosystem — trading bots, re
 4. **Enable accountability** — When an agent causes harm, there is no way to trace responsibility.
 5. **Create economic deterrence** — Malicious agents face no financial consequences.
 
-Existing standards ([ERC-725](./erc-725.md), [ERC-735](./erc-735.md), W3C DIDs) address human identity but not AI agent-specific concerns: capability declaration, code auditability, economic staking, and agent-specific reputation. This standard fills that gap.
+Existing standards ([ERC-725](./eip-725.md), [ERC-735](./eip-735.md), W3C DIDs) address human identity but not AI agent-specific concerns: capability declaration, code auditability, economic staking, and agent-specific reputation. This standard fills that gap.
 
 ## Specification
 
@@ -166,8 +166,8 @@ The accountability anchor (email/domain) remains non-public but queryable throug
 
 This standard does not conflict with existing ERC standards. It is compatible with:
 
-- **[ERC-725](./erc-725.md)** (Identity): AgentRegistry can serve as an identity provider for [ERC-725](./erc-725.md) claims.
-- **[ERC-165](./erc-165.md)** (Interface Detection): Implementations SHOULD support [ERC-165](./erc-165.md) for interface detection.
+- **[ERC-725](./eip-725.md)** (Identity): AgentRegistry can serve as an identity provider for [ERC-725](./eip-725.md) claims.
+- **[ERC-165](./eip-165.md)** (Interface Detection): Implementations SHOULD support [ERC-165](./eip-165.md) for interface detection.
 - **EAS** (Ethereum Attestation Service): Agent attestations can be bridged to EAS schemas.
 
 ## Test Cases