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/sxzgroup/orbit-q/agents-mdgit clone --depth 1 https://github.com/sxzgroup/ORBIT-QWrote 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/sxzgroup/orbit-q/agents-md)<a href="https://agentmods.dev/instructions/sxzgroup/orbit-q/agents-md"><img src="https://agentmods.dev/badge/instructions/sxzgroup/orbit-q/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 | $0.04070 | $0.04070 |
| Opus 5 | $0.02035 | $0.02035 |
| Sonnet 5 | $0.00814 | $0.00814 |
| Haiku 4.5 | $0.00407 | $0.00407 |
Grade B, and why
ORBIT-Q AGENTS.md scanned grade B with 1 finding 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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
--dangerously-skip-permissions cannot be used with root/sudo privileges for security reasons How it starts
The opening of the file, as written. The whole thing — 419 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This repository hosts a Harbor benchmark suite for 12 standard quantum challenge tasks.
Active tasks:
tasks/challenge-01
...
tasks/challenge-12
Do not use the removed physical-sciences/physics/... smoke path as the active benchmark.
Quick Bootstrap
Run all commands from the repository root.
Use the local Harbor Python environment if it exists:
./.conda/harbor-py312/bin/harbor --help
If this environment is absent, create or install Harbor outside this repository, then keep using the repo root on PYTHONPATH so Harbor can import local adapters.
Build or refresh the framework-specific Docker image used by both agent and verifier. This is the first command to run on a new machine after Docker is available:
FRAMEWORK=tensorcircuit bash scripts/build_challenge_quantum_image.sh
The default TensorCircuit tag is:
challenge-benchmark-quantum-tensorcircuit:py311
Verify that the image contains Codex CLI and Claude Code:
docker run --rm challenge-benchmark-quantum-tensorcircuit:py311 \
sh -lc 'codex --version && claude --version'
Generate framework prompt files and canonical tasks only when templates or upstream problem files change:
python3 scripts/generate_framework_prompts.py --framework tensorcircuit pennylane torchquantum
python3 scripts/generate_tc_challenge_tasks.py
By default the generator expects the upstream challenge-suite source repo next to this repository at ../tensorcircuit/examples/challenge_suite. Override it with TC_CHALLENGE_SUITE_SOURCE or --source if needed.
Do not regenerate tasks/challenge-* while a Harbor job is running. Local Harbor uses the live task directory as Docker context and compose project directory.
Framework Image Strategy
The benchmark intentionally uses stable framework-specific local images instead of asking Harbor to rebuild each task environment. Tasks do not carry Dockerfiles. Image definitions and framework Python dependencies are maintained under:
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.
- 4d ago First seen · 419 lines · 4,070 tokens per session scan B 1a943db53312
ORBIT-Q AGENTS.md is an instructions file published in the GitHub repository sxzgroup/ORBIT-Q (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 4,070 tokens to every session, about $0.0204 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
bio-gene-to-reference-tree copilot-instructions.md
Copilot instructions for Hongda-Zhao/bio-gene-to-reference-tree, a project described as: Auditable agent skill for resolving protein queries, selecting references, and planning reproducible phylogenetic trees.
braina GEMINI.md
Instructions for brainets/braina, covering project: braina (brain interaction analysis), 1. project context & purpose, 2. commands, verify environment (all core dependencies) and run the verification test suite for frites + hoi.
research-automation CLAUDE.md
Instructions for lucafusarbassini/research-automation, covering ricet - research automation framework, project overview, claude-flow mcp, workflow habits and file organization.
shannon-prover CLAUDE.md
Claude Code instructions for SkyShannonProver/shannon-prover, covering shannon prover: claude entry point, current boundary, easycrypt environment, eval safety and current documentation.
SciCrucible CLAUDE.md
Claude Code instructions for Xinyang-Li666/SciCrucible, covering 科学知识库, 知识库结构, 可用命令, 项目目录 and 工作原则.
torchcell CLAUDE.md
Claude Code instructions for Mjvolk3/torchcell, covering vision -- the virtual cell (north star), for local configs, git worktrees, programming guide and provenance & reproducibility.