weld copilot-instructions.md

A coding instruction that requires architecture-sensitive changes in weld to follow the principles documented in docs/architecture/principles.md.

In plain words
What is it for?
Use it when changing weld's architecture or reviewing a change that depends on those documented principles.
Why use it?
It points developers to the project's design rules before making changes that could affect its overall structure.

Instructions file for GitHub Copilot

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/configflux/weld/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/configflux/weld

Made for: GitHub Copilot.

Per session 19 This file is loaded in full into every session.
When invoked 19 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.00019 $0.00019
Opus 5 $0.00010 $0.00010
Sonnet 5 $0.00004 $0.00004
Haiku 4.5 $0.00002 $0.00002

Measured yesterday against content hash b727b4c4def5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

weld 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 yesterday.

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.

examples/agent-graph-demo/.github/copilot-instructions.md · 4 lines

What it actually says

Copilot Instructions

Use @docs/architecture/principles.md for architecture-sensitive changes.

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. yesterday First seen · 4 lines · 19 tokens per session scan A b727b4c4def5

Subscribe to this mod's changes

weld copilot-instructions.md is an instructions file published in the GitHub repository configflux/weld (6 stars, last pushed 2d ago), licensed Apache-2.0. It adds 19 tokens to every session, about $0.0001 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-31.