Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/keyhana/c166-ghidra-module/agents-mdgit clone --depth 1 https://github.com/keyhana/c166-ghidra-moduleWrote 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.
[](https://agentmods.dev/instructions/keyhana/c166-ghidra-module/agents-md)<a href="https://agentmods.dev/instructions/keyhana/c166-ghidra-module/agents-md"><img src="https://agentmods.dev/badge/instructions/keyhana/c166-ghidra-module/agents-md.svg" alt="Measured on agentmods" height="20"></a>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.00900 | $0.00900 |
| Opus 5 | $0.00450 | $0.00450 |
| Sonnet 5 | $0.00180 | $0.00180 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
c166-ghidra-module 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
C166 Ghidra Module
Ghidra processor extension for Infineon C166/C167 devices. Core risk: translating 16-bit operands into correct 24-bit addresses without changing instruction or decompiler semantics.
Working Rules
- Trace every caller and representation affected by a change: SLEIGH semantics, program context, analyzer references, injected p-code, and decompiler output.
- Before changing instruction encoding, flags, addressing, or timing windows,
read relevant instruction in
c166ism.md. Treat manual as architectural source of truth; existing implementation may contain bug being fixed. - Reuse existing SLEIGH subtable, analyzer, injector, or script path before adding another translation layer.
- Keep generated files out of source changes. Gradle compiles staged
c166.slafor headless tests and removes source-tree copy before extension builds. - Leave smallest runnable regression that fails on original bug and checks externally visible result: disassembly, reference target, p-code, or decompilation.
- Always checkout to main and fetch upstream changes and start from a new branch before starting to change code.
Addressing Invariants
DPP: (DPP[offset >> 14] << 14) | (offset & 0x3FFF)
EXTP: (page << 14) | (offset & 0x3FFF)
EXTS: (segment << 16) | (offset & 0xFFFF)
- Resolution priority: EXTS, EXTP, DPP, then raw offset when context is unknown.
- EXTP uses low 14 offset bits; EXTS uses full 16-bit offset.
- EXTP/EXTS apply only for encoded instruction-count window.
- Read DPP and extension registers at instruction address context.
- Never derive missing DPP value from operand selector; that creates phantom refs.
- Listing references do not affect decompiler. Change decompiler behavior through
p-code (
segment()/injectors) orJumpTable.writeOverride().
Change Routing
| Change | Primary location |
|---|---|
| Instruction encoding, semantics, flags | data/languages/c166.sinc |
| Calling convention or callother mapping | data/languages/c166.cspec |
| Language/compiler registration | data/languages/c166.ldefs |
| SFR symbols or segment operation | data/languages/*.pspec |
| Static address references | C166AddressAnalyzer.java, GetPagedOffset.java |
| Register-offset p-code | RegOffsetAddr.java |
| Custom p-code operation | PcodeInject.java plus matching injector |
| Interactive repair workflow | ghidra_scripts/ |
| Headless regression | tests/headless/ and build.gradle |
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.
- 6d ago First seen · 83 lines · 900 tokens per session scan A 73ccd239abd9
c166-ghidra-module AGENTS.md is an instructions file published in the GitHub repository keyhana/c166-ghidra-module (55 stars, last pushed 12d ago), licensed MIT. It adds 900 tokens to every session, about $0.0045 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-30.
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).
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.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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.