Borrowing it
Nothing to install: this file belongs to AcKeskin/contexture. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AcKeskin/contexture/main/.github/instructions/web.instructions.mdgit clone --depth 1 https://github.com/AcKeskin/contextureWrote 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/ackeskin/contexture/web)<a href="https://agentmods.dev/instructions/ackeskin/contexture/web"><img src="https://agentmods.dev/badge/instructions/ackeskin/contexture/web/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.
<a href="https://agentmods.dev/instructions/ackeskin/contexture/web"><img src="https://agentmods.dev/badge/instructions/ackeskin/contexture/web.svg" alt="Reviewed on agentmods" width="80" 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.00505 | $0.00505 |
| Opus 5.5 | $0.00202 | $0.00202 |
| Sonnet 5.5 | $0.00101 | $0.00101 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
contexture web.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 1mo 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
web rules
Auto-loaded by Copilot when editing files matching
**/*.{html,css,jsx,tsx}. Generated fromarchitectural-rules/web/— do not hand-edit.
Web async discipline
- All async work is explicit.
async/awaitat call sites, not fire-and-forget. - No implicit side effects in render / effect hooks beyond what the contract allows (e.g. React
useEffectcleanup). - Cancelation is part of the design — every long-running async operation has a cancel path (AbortController, effect cleanup, subscription disposal).
- Errors in async work are handled explicitly. Unhandled promise rejections are bugs, not warnings to ignore.
Why: async bugs dominate production incidents in web apps. Explicit patterns catch them at review time. Source: MDN AbortController; WHATWG HTML unhandledrejection.
Web layering
- Four layers, strict dependencies inward:
- Domain — pure business logic, framework-agnostic.
- State — application state shape, reducers / stores.
- Transport — HTTP, WebSocket, other I/O adapters.
- UI — presentation, framework components.
- Domain must have no React / Vue / Angular / framework imports.
- UI talks to State; State talks to Transport; Transport talks to Domain types (not the other way).
- Avoid magic globals. No module-level mutable state.
- This vocabulary refines universal/layering for web apps: Domain = Core, Transport = Integration, UI = UI; State is web's extra layer between UI and Transport (Platform rarely appears). Universal/layering owns the base vocabulary.
Why: frameworks churn. Domain logic bound to framework primitives dies with the framework. Source: ports-and-adapters / clean-architecture layering.
Web state flow
- State flow is predictable: state in → render out → action → state in. Unidirectional.
- No magic globals. No
window.*mutation for app state. - State changes are explicit and traceable — every change has an identifiable source (action, event handler, effect).
- Prefer derived state over duplicated state. If two pieces of state can disagree, one is wrong.
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.
- 1mo ago First seen · 40 lines · 505 tokens per session scan A 8240fd2b73d4
contexture web.instructions.md is an instructions file published in the GitHub repository AcKeskin/contexture (2 stars, last pushed 2mo ago), licensed MIT. It adds 505 tokens to every session, about $0.0020 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.