Fathom: Instructions file for Codex

AGENTS.md

Fathom AGENTS.md is an instructions file for Codex, OpenCode from Tideshift-Labs/Fathom. It costs 683 tokens per session, scanned A, original, MIT.

Development instructions for Fathom, a Rider plugin, with guidance on documentation, failed inspection approaches, and accessing closed-source JetBrains APIs through reflection.

In plain words
What is it for?
Use it when developing or debugging the Fathom Rider plugin, especially its code inspections and Unreal Engine companion integration.
Why use it?
It helps contributors avoid known dead ends and correctly find runtime APIs whose names or access methods may differ from expectations.

Instructions file for CodexOpenCode

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

This is Tideshift-Labs/Fathom's own configuration. It tells Codex and OpenCode how to work on Fathom 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 Fathom configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Tideshift-Labs/Fathom. 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/Tideshift-Labs/Fathom/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/Tideshift-Labs/Fathom

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 Fathom AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/tideshift-labs/fathom/agents-md/github.svg)](https://agentmods.dev/instructions/tideshift-labs/fathom/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/tideshift-labs/fathom/agents-md"><img src="https://agentmods.dev/badge/instructions/tideshift-labs/fathom/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 Fathom AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/tideshift-labs/fathom/agents-md"><img src="https://agentmods.dev/badge/instructions/tideshift-labs/fathom/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 683 This file is loaded in full into every session.
When invoked 683 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.00683 $0.00683
Opus 5.5 $0.00273 $0.00273
Sonnet 5.5 $0.00137 $0.00137
Haiku 4.5 $0.00068 $0.00068

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

Security

Grade A, and why

Fathom 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 · 46 lines

How it starts

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

Agent Instructions: Fathom (Rider Plugin)

Style

  • Never use emdashes (—). Rephrase instead.

Key Documentation

  • README.md: Architecture, HTTP API, build commands, development workflow.
  • docs/LEARNINGS.md: Dead-end approaches and hard-won lessons. Read the "DEAD END" sections before attempting alternative inspection APIs. Multiple approaches (RunLocalInspections for C++, ForceReHighlight for non-open files, SolutionAnalysisManager as a component) were fully explored and proven not to work.
  • docs/ue-companion-plugin.md: Blueprint audit architecture, explaining how the Rider plugin and UE companion plugin couple via filesystem conventions.

Reflection Gotchas

This plugin accesses closed-source JetBrains APIs via reflection. Key pitfalls:

  • GetComponent<T>() is an extension method, not an instance method on ISolution. You must search interfaces, base types, then scan assemblies for static extension methods.
  • ResolveComponent(Type) helper exists for component resolution when generic type parameters don't work at runtime.
  • Type names may differ from guesses. Use diagnostic dumps (stderr or HTTP response with &debug=true) when debugging reflection failures.
  • Blueprint APIs (UE4AssetsCache, UE4SearchUtil) are accessed via reflection on JetBrains.ReSharper.Feature.Services.Cpp.dll with no compile-time reference.

UE Project Detection

Two approaches are used, depending on the need:

  • Lightweight: Check for .uproject files in the solution directory. Fast, no reflection needed.
  • Full info: GetUEProjectInfo() via ICppUE4SolutionDetector reflection. Returns engine path, project path, target platform. Engine path comes from UnrealContext.Path property.

Commandlet Detection

When the Rider plugin spawns UnrealEditor-Cmd.exe -run=BlueprintAudit, it looks for "unknown commandlet" patterns in the process output to detect whether the companion UE plugin is installed. If the commandlet isn't registered (plugin not installed), the output contains this pattern and the refresh fails gracefully.

Read the full file on GitHub · 46 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. 2mo ago First seen · 46 lines · 683 tokens per session scan A 036df4907fd7

Subscribe to this mod's changes

Fathom AGENTS.md is an instructions file published in the GitHub repository Tideshift-Labs/Fathom (14 stars, last pushed 2mo ago), licensed MIT. It adds 683 tokens to every session, about $0.0027 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-30.

Related

Other instructions, from other repositories

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 · 9,715 tokens

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,461 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens