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/thiagoguislotti/copilot-instructions/artifact-layoutgit clone --depth 1 https://github.com/ThiagoGuislotti/copilot-instructionsWrote 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/thiagoguislotti/copilot-instructions/artifact-layout)<a href="https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/artifact-layout"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/artifact-layout.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 | $0.00510 | $0.00510 |
| Opus 5 | $0.00255 | $0.00255 |
| Sonnet 5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
copilot-instructions artifact-layout.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 5d 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.
What it actually says
Build And Deployment Artifact Layout
Purpose
- Standardize non-versioned repository outputs so generated files do not spread across ad-hoc folders.
- Keep build, publish, packaging, generated client, coverage, and deployment-ready outputs in predictable non-versioned locations.
Canonical Directories
.build/- transient build outputs
- generated intermediate files
- generated client assets such as
.httpfiles - local diagnostics that are useful during development but are not deployment packages
.deployment/- deployment-ready publish outputs
- packaged artifacts intended for runtime validation, containerization, or release staging
- test and coverage exports when they represent deployment/release evidence rather than source assets
Hard Rules
- Do not invent new top-level non-versioned artifact folders when
.build/or.deployment/is sufficient. - Do not scatter generated outputs under source folders when the artifact is not source of truth.
- Keep both folders ignored by Git.
- Keep source trees clean after builds, tests, code generation, and packaging.
Usage Guidance
- Use
.build/for local build-oriented outputs that can be regenerated cheaply. - Use
.deployment/for publish/release/package outputs that represent what would be deployed or attached to delivery artifacts. - Keep nested organization explicit, for example:
.build/generated/.build/http/.build/logs/.deployment/release/.deployment/tests/.deployment/packages/
.NET Guidance
- Redirect generated and publish outputs to
.build/or.deployment/whenever the project or script supports explicit output paths. - Prefer:
dotnet build -o .build/...for temporary build outputsdotnet publish -o .deployment/...for deployable outputs
Maintenance Guidance
- Use
scripts/maintenance/clean-build-artifacts.ps1to clean.build/,.deployment/,bin/, andobj/. - When creating new scripts or templates that emit generated files, default their outputs into one of these canonical directories unless repository context requires a stronger exception.
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.
- 5d ago First seen · 48 lines · 510 tokens per session scan A 150c9153667b
copilot-instructions artifact-layout.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 510 tokens to every session, about $0.0026 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.
Other instructions, from other repositories
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.
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 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).
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.
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.
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).