agentmods.dev

SRAgent: Instructions file for Codex

AGENTS.md

SRAgent AGENTS.md is an instructions file for Codex, OpenCode from ArcInstitute/SRAgent. It costs 628 tokens per session, scanned A, original, MIT.

Repository instructions for SRAgent, a Python tool with a command-line interface, data tools, workflows, and tests.

In plain words
What is it for?
Following the project’s folder structure, running its tests and command-line checks, building its Docker image, and matching its Python naming and style rules.
Why use it?
They give an agent clear rules for how the project is organised, built, tested, and written, reducing guesswork when changing the code.

Instructions file for CodexOpenCode

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

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

not rated 204repo 3mo ago A scan 628 tokens original MIT
View source ↗ ArcInstitute/SRAgent
Reuse

Borrowing it

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

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 SRAgent AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/arcinstitute/sragent/agents-md"><img src="https://agentmods.dev/badge/instructions/arcinstitute/sragent/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 628 This file is loaded in full into every session.
When invoked 628 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.00628 $0.00628
Opus 5.5 $0.00251 $0.00251
Sonnet 5.5 $0.00126 $0.00126
Haiku 4.5 $0.00063 $0.00063

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

Security

Grade A, and why

SRAgent 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 2mo 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 · 37 lines

How it starts

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

Repository Guidelines

Project Structure & Module Organization

  • SRAgent/: Python package (CLI in cli/, agent logic in agents/, tools in tools/, workflows in workflows/, DB helpers in db/).
  • tests/: Pytest suite mirroring package layout (e.g., tests/agents/, tests/workflows/).
  • scripts/: Standalone utilities and evaluation helpers.
  • assets/: Images used in docs.
  • Root files: pyproject.toml (build), Dockerfile, README.md, .env (optional), .github/workflows/ (CI).

Build, Test, and Development Commands

  • Install (user): pip install .
  • Install (dev): pip install -e ".[dev]"
  • Run tests: pytest tests/
  • CLI help: SRAgent --help
  • Example run: SRAgent entrez "Convert GSE121737 to SRX accessions"
  • Docker (optional): docker build -t sragent . then docker run --rm -e OPENAI_API_KEY -e ANTHROPIC_API_KEY sragent --help

Coding Style & Naming Conventions

  • Python ≥ 3.11; follow PEP 8 with 4‑space indents and descriptive names.
  • Names: modules/functions snake_case, classes CamelCase, constants UPPER_SNAKE_CASE.
  • Prefer type hints and docstrings on public functions; keep functions small and focused.
  • No repo‑enforced linter; keep style consistent with nearby code and avoid introducing new tooling/config without discussion.

Testing Guidelines

  • Framework: pytest. Place tests under tests/ with files named test_*.py and test functions test_*.
  • Mirror CLI and workflow behavior; see tests/test_cli_help.py for a pattern to validate subcommand help and exit codes.
  • Add tests for new features and edge cases; avoid network‑dependent tests unless mocked.

Commit & Pull Request Guidelines

  • Commits: concise, imperative subject; include context in the body when changing behavior or interfaces (e.g., “Add disease‑ontology agent”).
  • PRs: clear description, rationale, and usage notes; link issues when applicable. Include example CLI invocations or sample output for user‑facing changes.
  • CI: GitHub Actions runs pytest on Python 3.11/3.12 for main and dev. PRs must be green before merge.

Read the full file on GitHub · 37 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. 2mo ago First seen · 37 lines · 628 tokens per session scan A ff544f0cdad4

Subscribe to this mod's changes

SRAgent AGENTS.md is an instructions file published in the GitHub repository ArcInstitute/SRAgent (204 stars, last pushed 3mo ago), licensed MIT. It adds 628 tokens to every session, about $0.0025 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

SRAgent AGENTS.md compared with instructions from other repositories

SRAgent AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
SRAgent AGENTS.mdArcInstitute/SRAgentInstructions file2043mo agoMITA628Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode