What is positioning-bridge AGENTS.md?

Project-specific instructions stored in an AGENTS.md file for positioning-bridge. They define how contributors should change and verify a project that checks evidence-backed positioning in content workflows.

Use them when contributing to positioning-bridge, especially when changing evaluation decisions, architecture, tests, or documentation.

They reduce uncertainty when changing the code by recording the product contract, architecture boundaries, testing expectations, and verification command.

How shashank-sn/positioning-bridge configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to shashank-sn/positioning-bridge. 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/shashank-sn/positioning-bridge/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/shashank-sn/positioning-bridge

Made for: Codex, OpenCode.

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/shashank-sn/positioning-bridge/agents-md/github.svg)](https://agentmods.dev/instructions/shashank-sn/positioning-bridge/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/shashank-sn/positioning-bridge/agents-md"><img src="https://agentmods.dev/badge/instructions/shashank-sn/positioning-bridge/agents-md/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/shashank-sn/positioning-bridge/agents-md"><img src="https://agentmods.dev/badge/instructions/shashank-sn/positioning-bridge/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 112 This file is loaded in full into every session.

When invoked 112 The same file — it is already loaded in full.

Security scan A 0 findings. 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.00112	$0.00112
Opus 5.5	$0.00045	$0.00045
Sonnet 5.5	$0.00022	$0.00022
Haiku 4.5	$0.00011	$0.00011

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

Security

Grade A, and why

positioning-bridge AGENTS.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 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.

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.

AGENTS.md · 11 lines

What it actually says

contributor instructions

treat docs/plans/2026-08-23-positioning-bridge-requirements.md as the product contract.
preserve the dependency direction in config/architecture.policy.json.
keep deterministic and model-assisted evidence separate in types, tests, and prose.
do not add network access, policy mutation, publishing, or a HYV dependency without a new architecture decision.
add a behavior-level test before changing an evaluation decision.
run npm run verify before calling a revision complete.

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 · 11 lines · 112 tokens per session scan A 0b8b1ed376c4

Subscribe to this mod's changes

positioning-bridge AGENTS.md is an instructions file published in the GitHub repository shashank-sn/positioning-bridge (0 stars, last pushed 6d ago), licensed MIT. It adds 112 tokens to every session, about $0.0004 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.

TypeScript content-governance mcp messaging model-context-protocol positioning

positioning-bridge AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
positioning-bridge AGENTS.mdshashank-sn/positioning-bridge	Instructions file	0	6d ago	MIT	A	112	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

positioning-bridge: Instructions file for Codex