agentmods.dev

DecompilerServer copilot-instructions.md

Repository-specific instructions for DecompilerServer, a software project for decompiling and comparing code. They describe its architecture, tool conventions, search methods, and verification expectations.

In plain words
What is it for?
They are for guiding work with the project’s MCP tools, symbol searches, member resolution, decompilation, structured results, and repository documentation.
Why use it?
They help an agent make changes that fit the project’s existing structure and use the intended tools for finding and comparing code.

Instructions file for GitHub Copilot

93 16d ago A scan 559 tokens original MIT
View the source file pardeike/DecompilerServer
Install

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.

agentmods
npx agentmods add instructions/pardeike/decompilerserver/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/pardeike/DecompilerServer

Made for: GitHub Copilot.

Per session 559 This file is loaded in full into every session.
When invoked 559 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00559 $0.00559
Opus 5 $0.00280 $0.00280
Sonnet 5 $0.00112 $0.00112
Haiku 4.5 $0.00056 $0.00056

Measured 2d ago against content hash 55cb249dbb3a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

DecompilerServer copilot-instructions.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 2d 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.

.github/copilot-instructions.md · 53 lines

How it starts

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

DecompilerServer Copilot Instructions

Read these files first:

  • ARCHITECTURE.md for durable technical rules and contracts
  • README.md for user-facing workflow
  • TODO.md for backlog

Repository-Specific Rules

  • MCP tools live as static methods under Tools/.
  • Tools should return via ResponseFormatter.TryExecute(...).
  • Discovery/search tools should route with using var session = ToolSessionRouter.GetForContext(...).
  • memberId follow-up tools should route with using var session = ToolSessionRouter.GetForMember(...).
  • Reuse TypeSurfaceComparer for type-surface semantics instead of duplicating compare logic.
  • Use DecompilerService.DecompileEntitySnippet(...) for focused compare body retrieval.
  • Prefer structured JSON output over pre-rendered diff text for overview commands.
  • For unknown foreign code, start with search_symbols for fragments. For fully-qualified or XML-doc-like guessed symbols, start with resolve_member_id so structured member_not_found diagnostics can resolve the type and suggest candidates.
  • After a type resolves, use list_members/get_members_of_type, then source or caller/callee tools. Do not fall back to shell scans after one bad member guess unless MCP diagnostics are exhausted.

Workspace and Compare Expectations

  • Assume multi-context workspace support is the primary model.
  • Preserve stable member ID format: <mvid-32hex>:<token-8hex>:<kind-code>.
  • compare_contexts is structural. changed means direct member surface changed.
  • compare_symbols(compareMode: "body") is method-only and should stay opt-in.
  • Do not broaden compare semantics casually; update ARCHITECTURE.md if a durable contract changes.

Testing

  • Use xUnit and real compiled test assemblies.
  • Tests/ServiceTestBase.cs is the base fixture for service-level tests.
  • Add dedicated *ToolTests.cs files for MCP tool behavior.
  • Use Tests/TemporaryAssemblyBuilder.cs for controlled version-drift and compare tests.
  • When tests need workspace-aware behavior, register DecompilerWorkspace in the test service provider.

Read the full file on GitHub · 53 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. 2d ago First seen · 53 lines · 559 tokens per session scan A 55cb249dbb3a

Subscribe to this mod's changes

DecompilerServer copilot-instructions.md is an instructions file published in the GitHub repository pardeike/DecompilerServer (93 stars, last pushed 16d ago), licensed MIT. It adds 559 tokens to every session, about $0.0028 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.

ResearchTestingWriting and docs
Related

Other instructions, from other repositories

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,182 tokens

buildNext

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

next.js 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

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

spec-kit 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.

github/spec-kit · 7,040 tokens

langchain 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,345 tokens