Borrowing it
Nothing to install: this file belongs to RobinOppenstam/sema-evals. 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/RobinOppenstam/sema-evals/main/AGENTS.mdgit clone --depth 1 https://github.com/RobinOppenstam/sema-evalsWrote 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/robinoppenstam/sema-evals/agents-md)<a href="https://agentmods.dev/instructions/robinoppenstam/sema-evals/agents-md"><img src="https://agentmods.dev/badge/instructions/robinoppenstam/sema-evals/agents-md.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.1 | $0.00286 | $0.00286 |
| Opus 5 | $0.00143 | $0.00143 |
| Sonnet 5 | $0.00057 | $0.00057 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
sema-evals 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 7d 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
Repository instructions
This repository evaluates semantic coordination mechanisms. Treat research validity as a product requirement.
Non-negotiable experiment rules
- Never describe deterministic harness output as evidence that Sema improves model performance.
- Keep pattern content identical between equal-information prose and Sema conditions. Isolate content, addressing, and enforcement effects.
- Choose and document one primary endpoint before a confirmatory run.
- Preserve every run, including failures, timeouts, and malformed outputs.
- Record prompt, dataset, model, implementation, Sema version, vocabulary root, scorer, and protocol fingerprints in result manifests.
- Report wire bytes, hydration/context tokens, and total model tokens separately. A short reference is not automatically a context-token saving.
- Prefer deterministic validators. Blind subjective judges to the experiment condition and never use an LLM judge as the only scorer.
- Do not use live trading capital in an experiment. Historical replay and paper execution come first.
Engineering rules
- Use pnpm and Node.js 22 or newer.
- Keep TypeScript strict and avoid
any. - Put reusable code in
packages/; experiment-specific policy belongs underexperiments/. - Generated result bundles belong under
results/and remain untracked unless intentionally promoted into a dated public report. - Run
pnpm checkbefore handing off 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.
- 7d ago First seen · 32 lines · 286 tokens per session scan A fa46a2ee0d53
sema-evals AGENTS.md is an instructions file published in the GitHub repository RobinOppenstam/sema-evals (5 stars, last pushed 1mo ago), licensed MIT. It adds 286 tokens to every session, about $0.0014 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
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).
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.
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).
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.