Borrowing it
Nothing to install: this file belongs to Maleick/AutoResearch. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Maleick/AutoResearch/main/AGENTS.mdgit clone --depth 1 https://github.com/Maleick/AutoResearchWrote 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/maleick/autoresearch/agents-md)<a href="https://agentmods.dev/instructions/maleick/autoresearch/agents-md"><img src="https://agentmods.dev/badge/instructions/maleick/autoresearch/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.1 | $0.00389 | $0.00389 |
| Opus 5 | $0.00195 | $0.00195 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
AutoResearch 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.
What it actually says
Auto Research Agent Guide
Project Purpose
Auto Research is an OpenCode and Hermes Agent workflow bundle plus npm package for structured autonomous improve-verify loops.
Source of Truth
- Runtime source lives in
src/. - OpenCode commands live in
commands/. - The Auto Research skill bundle lives in
skills/autoresearch/. - The Hermes Agent skill bundle and integration docs live in
skills/hermes/. - Shell hooks live in
hooks/. - OpenCode package metadata lives in
.opencode-plugin/plugin.json. - Installation, architecture, and release docs live in
docs/andwiki/.
Development Rules
- Build context from existing files before changing behavior.
- Prefer the smallest correct change.
- Do not commit, tag, push, create releases, or publish packages unless the user explicitly asks.
- Do not commit runtime artifacts from
.autoresearch/or generated result files. - Keep
VERSION,package.json,package-lock.json,src/constants.ts, and.opencode-plugin/plugin.jsonaligned for releases. - When Hermes cron,
delegate_task, model routing, or install behavior changes, keepREADME.md,INSTALL.md,docs/,wiki/, andskills/hermes/aligned.
Security Rules
- Do not add install flows that pipe remote scripts into a shell.
- Keep package contents guarded by
hooks/verify-package.sh. - Do not hardcode secrets, tokens, credentials, or private paths.
- Pass shell variables into inline scripts through environment variables or argv, not by interpolating into source code.
Verification
Run the focused relevant checks before claiming work is complete. Release-prep changes should run:
npm audit --audit-level=moderate
npm run typecheck
npm run build
npm run verify:pack
npm test
npm pack --dry-run
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.
- 7d ago First seen · 45 lines · 389 tokens per session scan A 91d030064fb6
AutoResearch AGENTS.md is an instructions file published in the GitHub repository Maleick/AutoResearch (10 stars, last pushed 1mo ago), licensed MIT. It adds 389 tokens to every session, about $0.0019 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-31.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.