Borrowing it
Nothing to install: this file belongs to huangzhonglv/hep-workflow. 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/huangzhonglv/hep-workflow/main/AGENTS.mdgit clone --depth 1 https://github.com/huangzhonglv/hep-workflowWrote 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/huangzhonglv/hep-workflow/agents-md)<a href="https://agentmods.dev/instructions/huangzhonglv/hep-workflow/agents-md"><img src="https://agentmods.dev/badge/instructions/huangzhonglv/hep-workflow/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.01658 | $0.01658 |
| Opus 5 | $0.00829 | $0.00829 |
| Sonnet 5 | $0.00332 | $0.00332 |
| Haiku 4.5 | $0.00166 | $0.00166 |
Grade A, and why
hep-workflow 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- hep-workflow CLAUDE.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hep-workflow
Read by all AI agents working in this repo. Claude Code loads
CLAUDE.md; Codex and other tooling loadAGENTS.md. The two files are kept byte-identical bytests/contract/test_top_level_docs_byte_identical.py.
Project
A skill-based agent workflow for high-energy physics phenomenology — model proposal → symbolic calculation (Package-X / Mathematica) → numerical scans → publication-grade exclusion plots.
The repo ships skill definitions and validation tooling, not a runtime application. Most edits change schemas, skill prompts, helper scripts, or fixtures, and the test/validator layer is the contract surface.
Common commands
Setup (one-time):
python3 -m venv .venv && source .venv/bin/activate
python3 -m pip install -r requirements-dev.txt
The three validation layers — all must be green before any commit lands:
python3 scripts/validate_examples.py
python3 scripts/validate_workspace_projects.py
python3 -m pytest -q
When a skill tree or vendored shared helper changes, run the read-only mirror precondition before those three layers:
python3 scripts/sync_skill_mirrors.py --check
Run a single test or one layer:
python3 -m pytest -q tests/contract
python3 -m pytest -q tests/integration/test_minimal_scan.py
End-to-end suite (requires wolframscript; gated):
python3 -m pytest -q tests/e2e --run-e2e
Project-level contracts (load-bearing)
These rules apply project-wide. Full text in docs/contracts/. The summaries
here are pointers, not duplicates — never copy contract bodies into this file.
| Contract | One-line rule | Full text |
|---|---|---|
| Mirror invariants | .claude/skills/ ↔ .agents/skills/ byte-identical; orchestrator .md ↔ .toml content-equivalent; CLAUDE.md ↔ AGENTS.md byte-identical |
docs/contracts/mirror-invariants.md |
| Canonical name rule | New canonical identifiers match ^[A-Za-z_][A-Za-z0-9_]*$ and are not Python hard keywords; workflow IDs follow their own patterns |
docs/contracts/canonical-name-convention.md |
| Content-addressed dependencies | New calculation, scan, and reproduction outputs bind exact declared input/code bytes; legacy evidence cannot support new scientific claims | docs/contracts/content-addressed-dependencies.md |
| Three-validator discipline | validate_examples + validate_workspace_projects + pytest -q must stay green on main |
docs/contracts/three-validator-discipline.md |
| Manifest history actions | New action requires synchronized update across schema + skills + orchestrator + tests | docs/contracts/manifest-history-actions.md |
| Transactional publication | Multi-path writers publish one coherent generation through lock + journal + CAS; interrupted state fails closed | docs/contracts/transactional-state-publication.md |
| Numerics manifest ownership | Manifest v2 owns files and dependency snapshots per analysis; aggregates are deterministic projections | docs/contracts/numerics-manifest-ownership.md |
| Skill / agent / script division | Mechanical → script; generation → skill; coordination → agent | docs/contracts/skill-agent-division.md |
| Honest reproduction principle | Calculations independently derived; disagreement reported as-is; never adjust tolerance to mask | docs/contracts/honest-reproduction-principle.md |
| Reproduction readiness | Per-target prerequisites are derived read-only from typed current evidence; formula targets do not consume model/calculation/scan state | docs/contracts/reproduction-readiness.md |
| Strict JSON trust boundaries | Duplicate keys, non-standard/non-finite numbers, overflow, and invalid UTF-8 fail before side effects | docs/contracts/strict-json.md |
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.
- 6d ago First seen · 150 lines · 1,658 tokens per session scan A 02633186665e
hep-workflow AGENTS.md is an instructions file published in the GitHub repository huangzhonglv/hep-workflow (9 stars, last pushed 1mo ago), licensed MIT. It adds 1,658 tokens to every session, about $0.0083 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).
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).
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.
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.