research-hub: Instructions file for Codex

AGENTS.md

research-hub AGENTS.md is an instructions file for Codex, OpenCode from WenyuChiou/research-hub. It costs 1,214 tokens per session, scanned A, original, MIT.

Repository instructions for OpenWiki, a system that generates recurring code documentation from an OpenWiki folder and its linked guidance.

In plain words
What is it for?
Use them to navigate the project's architecture, workflows, operations, integrations, testing, and source maps, then update the appropriate source material.
Why use it?
They tell the agent where to start and warn against editing generated documentation directly, reducing the risk of changes being overwritten.

Instructions file for CodexOpenCode

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

This is WenyuChiou/research-hub's own configuration. It tells Codex and OpenCode how to work on research-hub 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 research-hub configures →

Reuse

Borrowing it

Nothing to install: this file belongs to WenyuChiou/research-hub. 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/WenyuChiou/research-hub/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/WenyuChiou/research-hub

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 research-hub AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/wenyuchiou/research-hub/agents-md"><img src="https://agentmods.dev/badge/instructions/wenyuchiou/research-hub/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,214 This file is loaded in full into every session.
When invoked 1,214 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.01214 $0.01214
Opus 5.5 $0.00486 $0.00486
Sonnet 5.5 $0.00243 $0.00243
Haiku 4.5 $0.00121 $0.00121

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

Security

Grade A, and why

research-hub 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 3d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md · 96 lines

How it starts

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

OpenWiki

This repository uses OpenWiki for recurring code documentation. Start with openwiki/quickstart.md, then follow its links to architecture, workflows, domain concepts, operations, integrations, testing guidance, and source maps.

The OpenWiki GitHub Actions workflow (currently manual-dispatch only) refreshes the repository wiki. Do not hand-edit generated OpenWiki pages unless explicitly asked; prefer updating source code/docs and letting OpenWiki regenerate.

Code Review Rules

These rules apply only while conducting code review. They do not replace implementation or publication instructions or valid authorization for other tasks.

  • Review the actual diff at its stated base and head. Route checks by the affected paths and trace only the related source, consumer, schema, package, and CI contracts. Keep the existing OpenWiki generated-marker block byte for byte; do not hand-edit generated OpenWiki pages.
  • For PDF extraction, annotation, and reading-order paths, verify that glyph direction, margin notes, and reading order preserve the source's meaning and placement. If visual inspection is unavailable, report that verification gap explicitly; do not bypass the repository's file:// policy.
  • For source selection, acquisition, and saved artifacts, bind claims to the exact source identity and version. Treat access failure or missing provenance as unknown rather than as evidence about source content.
  • For Obsidian and HTML output, check semantic structure, links/frontmatter, encoding, and preservation of user-authored content. For demos, identify the canonical artifact and entrypoint and report its actual acceptance state; schema/checker success alone is not human acceptance.
  • Mock output and unrun experiments demonstrate only the behavior actually exercised; do not present them as live behavior, validated content, or an accepted demo. Keep schema checks distinct from human acceptance.
  • When affected code reads paths, renders HTML, or handles source/private data, check traversal, injection, and disclosure risks at the concrete input and output boundaries. Do not expose private source text in logs or fixtures.
  • For packaging changes, compare the source tree with the corresponding web, wheel, and skills_data contents for the changed assets. A source-tree check alone does not prove the distributed package contains the same files.
  • Findings need a concrete path and line/symbol, trigger, consequence, and evidence. Separate confirmed defects, hypotheses, and verification gaps; omit style-only preferences and follow the platform's required finding format.
  • A review task itself does not modify code, install dependencies, start paid models, or merge. Every PR merge needs separate explicit user consent after the user receives the review summary, actual test status, and remaining gaps.

Read the full file on GitHub · 96 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. 3d ago Changed · +50 lines · +630 tokens per session fa60b89c8cc3
  2. 15d ago Changed · +36 lines · +480 tokens per session 4ab8b119e518
  3. 1mo ago First seen · 10 lines · 104 tokens per session scan A adb1617c7509

Subscribe to this mod's changes

research-hub AGENTS.md is an instructions file published in the GitHub repository WenyuChiou/research-hub (66 stars, last pushed today), licensed MIT. It adds 1,214 tokens to every session, about $0.0049 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

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens