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/arcinstitute/sragent/agents-mdgit clone --depth 1 https://github.com/ArcInstitute/SRAgentWrote 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/arcinstitute/sragent/agents-md)<a href="https://agentmods.dev/instructions/arcinstitute/sragent/agents-md"><img src="https://agentmods.dev/badge/instructions/arcinstitute/sragent/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.00628 | $0.00628 |
| Opus 5 | $0.00314 | $0.00314 |
| Sonnet 5 | $0.00126 | $0.00126 |
| Haiku 4.5 | $0.00063 | $0.00063 |
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 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.
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.
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 incli/, agent logic inagents/, tools intools/, workflows inworkflows/, DB helpers indb/).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 .thendocker 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, classesCamelCase, constantsUPPER_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 namedtest_*.pyand test functionstest_*. - Mirror CLI and workflow behavior; see
tests/test_cli_help.pyfor 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
pyteston Python 3.11/3.12 formainanddev. PRs must be green before merge.
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 · 37 lines · 628 tokens per session scan A ff544f0cdad4
SRAgent AGENTS.md is an instructions file published in the GitHub repository ArcInstitute/SRAgent (182 stars, last pushed 1mo ago), licensed MIT. It adds 628 tokens to every session, about $0.0031 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-30.
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.