Building and running the .NET solution, configuring local secrets, understanding its ASP.NET Core and Aspire structure, and working on its Slack, browser, agent, and integration-test components.

It gives an agent the project context needed to build, run, and change the code consistently. It reduces guesswork about which projects to use, how services connect, and how tests should be written.

How thangchung/agent-engineering-experiment configures GitHub Copilot

Q: What is agent-engineering-experiment copilot-instructions.md?

A set of coding instructions for a .NET project, covering its design principles, project layout, commands, secrets, and message flow. It also recommends TDD, which means writing tests before or alongside code.

Reuse

Borrowing it

Nothing to install: this file belongs to thangchung/agent-engineering-experiment. 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/thangchung/agent-engineering-experiment/main/DotNetClaw/.github/copilot-instructions.md

Clone the repo

git clone --depth 1 https://github.com/thangchung/agent-engineering-experiment

Made for: GitHub Copilot.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/thangchung/agent-engineering-experiment/copilot-instructions/github.svg)](https://agentmods.dev/instructions/thangchung/agent-engineering-experiment/copilot-instructions)

Your own site

<a href="https://agentmods.dev/instructions/thangchung/agent-engineering-experiment/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/thangchung/agent-engineering-experiment/copilot-instructions/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/thangchung/agent-engineering-experiment/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/thangchung/agent-engineering-experiment/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,551 This file is loaded in full into every session.

When invoked 1,551 The same file — it is already loaded in full.

Security scan A 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.01551	$0.01551
Opus 5.5	$0.00620	$0.00620
Sonnet 5.5	$0.00310	$0.00310
Haiku 4.5	$0.00155	$0.00155

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

Security

Grade A, and why

agent-engineering-experiment copilot-instructions.md scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| `ExecTool.cs` | Shell exec with safety blocklist (rm, sudo, curl, etc.) |

DotNetClaw/.github/copilot-instructions.md · 119 lines

How it starts

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

Copilot Instructions

Principles

KISS / YAGNI / DRY / Boy-Scout. Simplest thing that works.
Red-green TDD whenever possible.

Build & Run

dotnet build dotnetclaw.slnx              # build all projects
dotnet run --project DotNetClaw/DotNetClaw.csproj  # standalone
dotnet run --project DotNetClaw.AppHost/DotNetClaw.AppHost.csproj  # Aspire (coffeeshop-cli + DotNetClaw)

Secrets: dotnet user-secrets set "Slack:BotToken" "xoxb-..." etc. See appsettings.json for all keys.

Solution Structure

DotNetClaw/            Main ASP.NET Core app (net10.0)
DotNetClaw.AppHost/    Aspire orchestration (local dev, registers coffeeshop-cli + dotnetclaw)
DotNetClaw.ServiceDefaults/  Shared Aspire defaults (health, OTel, resilience)
DotNetClaw.Tests/      Integration tests (console runner)

Architecture

Slack user         Browser user
    ↓ Socket Mode      ↓ HTTP POST /api/chat
SlackChannel.cs    WebChannel.cs
    └──────────┬───────┘
               ↓  sessionId + text
          ClawRuntime.cs
          ConcurrentDictionary<sessionId, AgentSession>
               ↓
          AIAgent  (MAF 1.0 + GitHub Copilot SDK 0.2.1)
          ReAct loop + streaming + tool calling
               ↓
          CopilotClient  (spawns copilot-cli via stdio JSON-RPC)
               ↓
          mind/  directory  →  system message

Session IDs — one AgentSession per unique ID:

Slack DM: slack:dm:{userId}, Slack mention: slack:{channelId}:{userId}
Web: web:{cookieGuid}

File Map

File	Role
`Program.cs`	Composition root — DI, AIAgent factory, channel wiring, endpoints
`ClawRuntime.cs`	Session store, per-session semaphore, `HandleAsync` / `HandleStreamingAsync`
`SlackChannel.cs`	Slack Socket Mode — DM + @mention handlers, extension methods
`WebChannel.cs`	HTTP chat API + static file serving, cookie-based sessions
`MindLoader.cs`	Loads `mind/SOUL.md` + agent files + working-memory → system message
`MemoryTool.cs`	Agent tools: `AppendLog`, `AddRule`, `SaveFact` (writes to `mind/.working-memory/`)
`ExecTool.cs`	Shell exec with safety blocklist (rm, sudo, curl, etc.)
`SkillLoaderTool.cs`	Skills via CLI or MCP from coffeeshop-cli (`ListSkills`, `LoadSkill`, `ListMenuItems`, `LookupCustomer`, `SubmitOrder`)
`wwwroot/index.html`	Browser chat UI (vanilla HTML + JS, no framework)

Read the full file on GitHub · 119 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.

2mo ago First seen · 119 lines · 1,551 tokens per session scan A 7a3c0b0124d2

Subscribe to this mod's changes

agent-engineering-experiment copilot-instructions.md is an instructions file published in the GitHub repository thangchung/agent-engineering-experiment (28 stars, last pushed 15d ago), licensed MIT. It adds 1,551 tokens to every session, about $0.0062 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

C# and .NET Languages ai-agents aiengineering foundry-local microsoft-agent-framework

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

agent-engineering-experiment: Instructions file for GitHub Copilot