Auto-Research-Skills: Instructions file for Codex

AGENTS.md

Auto-Research-Skills AGENTS.md is an instructions file for Codex, OpenCode from brycewang-stanford/Auto-Research-Skills. It costs 560 tokens per session, scanned A, original, CC0-1.0.

Repository instructions for coordinating multiple coding agents, editing safely, validating changes, and handing work over. They also explain which catalogue files are generated and how to rebuild them.

In plain words
What is it for?
Checking repository state before editing, making small compatible changes, rebuilding catalogue files, and following the project's validation workflow.
Why use it?
They reduce merge conflicts and prevent developers from manually changing files that are produced by the repository's build process.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is brycewang-stanford/Auto-Research-Skills's own configuration. It tells Codex and OpenCode how to work on Auto-Research-Skills itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Auto-Research-Skills configures →

Reuse

Borrowing it

Nothing to install: this file belongs to brycewang-stanford/Auto-Research-Skills. 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/brycewang-stanford/Auto-Research-Skills/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/brycewang-stanford/Auto-Research-Skills

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.

agentmods badge for Auto-Research-Skills AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/brycewang-stanford/auto-research-skills/agents-md/github.svg)](https://agentmods.dev/instructions/brycewang-stanford/auto-research-skills/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/brycewang-stanford/auto-research-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/brycewang-stanford/auto-research-skills/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.

agentmods 80×15 button for Auto-Research-Skills AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/brycewang-stanford/auto-research-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/brycewang-stanford/auto-research-skills/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 560 This file is loaded in full into every session.
When invoked 560 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00560 $0.00560
Opus 5.5 $0.00224 $0.00224
Sonnet 5.5 $0.00112 $0.00112
Haiku 4.5 $0.00056 $0.00056

Measured 7d ago against content hash d10ee762f09a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Auto-Research-Skills 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.

AGENTS.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Coordination

This repository is often edited by multiple agents at once. Keep changes small, observable, and easy to merge.

Before editing

  • Run git status --short --branch and inspect any dirty files before choosing a work area.
  • Do not overwrite or revert changes you did not make. If a dirty file is relevant, read it first and make the smallest compatible edit.
  • Prefer root-level scripts, docs, and generated catalog updates for maintenance work. Treat skills/, systems/, benchmarks/, and lists/ as vendored submodules unless the task is explicitly to update a submodule pointer.

Generated files

  • catalog/skills.json, catalog/skills.csv, catalog/CATALOG.md, and catalog/collections/*.md are generated by python tools/build_catalog.py. Do not hand-edit them.
  • After adding, removing, or updating submodules under skills/, regenerate the catalog and update README headline counts when scripts/check-repo.py asks for it.
  • See docs/TOOLING.md for the full generated-vs-source file map, the data pipeline, and the make/CI check matrix.
  • See docs/landscape-2026.md for the field map that explains the skills//systems//benchmarks//lists/ split and where vendored projects sit in the wider ecosystem. New-vendoring decisions are logged under docs/ (latest: docs/vendoring-2026-10-20.md).
  • After any submodule change also run make starter-kits; the kits depend on catalog content and safety findings.

Validation

Run these before handing off repo-level maintenance changes:

make check

Equivalent individual commands:

python scripts/check-repo.py
python -m unittest discover -s tests
python tools/build_catalog.py --check
./scripts/count-skills.sh

Use make safety-scan SAFETY_ROOTS=<path> for candidate skill collections. Findings are manual-review prompts, not automatic rejection.

Handoff

  • Summarize which files you changed and which checks passed.
  • Mention known warnings separately, especially the current skills/claude-scholar and skills/franklee-academic-research-skills nested-gitlink warnings (upstream layout, not actionable here).

Read the full file on GitHub · 59 lines

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.

  1. 7d ago Changed · +3 lines · +47 tokens per session d10ee762f09a
  2. 1mo ago First seen · 56 lines · 513 tokens per session scan A 8279644dea14

Subscribe to this mod's changes

Auto-Research-Skills AGENTS.md is an instructions file published in the GitHub repository brycewang-stanford/Auto-Research-Skills (230 stars, last pushed 2d ago), licensed CC0-1.0. It adds 560 tokens to every session, about $0.0022 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-30.

Related

Other instructions, from other repositories