Borrowing it
Nothing to install: this file belongs to Tx1207/hello-scholar. 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/Tx1207/hello-scholar/main/AGENTS.mdgit clone --depth 1 https://github.com/Tx1207/hello-scholarWrote 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/tx1207/hello-scholar/agents-md)<a href="https://agentmods.dev/instructions/tx1207/hello-scholar/agents-md"><img src="https://agentmods.dev/badge/instructions/tx1207/hello-scholar/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.
<a href="https://agentmods.dev/instructions/tx1207/hello-scholar/agents-md"><img src="https://agentmods.dev/badge/instructions/tx1207/hello-scholar/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.04017 | $0.04017 |
| Opus 5.5 | $0.01607 | $0.01607 |
| Sonnet 5.5 | $0.00803 | $0.00803 |
| Haiku 4.5 | $0.00402 | $0.00402 |
Grade A, and why
hello-scholar 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Engineering Guide
Deliver the smallest complete change that serves the current goal, with credible evidence and project facts another agent can continue from.
These rules apply to the project being worked on, regardless of its language, framework, or agent platform. Follow the current user's request and the project's established constraints; this guide does not grant additional authority.
Read Before You Write
- Before changing a project, read its existing README and contribution guide (such as CONTRIBUTING.md), then any relevant scoped instructions. Follow the current project's commands and constraints.
- Read the parts of each file that the change depends on, and the whole file when it is small or the change affects its structure; an unchanged version already read in context counts. Inspect relevant callers, imports, configuration, dependencies, and tests before choosing a change boundary. The cost of reading an existing entry point never justifies writing a parallel one.
- Reuse confirmed project patterns. Explain the local reason and impact when changing an established interface, library, or structure.
Think Before Coding
- Derive the work from the user's outcome, known facts, and real constraints. Separate those from inherited assumptions; resolve checkable questions from project evidence first.
- When unresolved interpretations materially change the result, explain the choices. Ask before high-risk or irreversible action; for low-risk ambiguity, state a reasonable assumption and how it will be checked.
- Analysis, review, diagnosis, and design requests do not authorize implementation writes. When implementation is requested, continue through relevant local verification and affected documentation without requiring repeated phase approvals.
- Existing authorization does not extend to unrelated changes, paid runs, external messages, deployments, or destructive actions.
- Own the whole authorized task: form a concrete approach, organize necessary steps, implement, verify, integrate findings, and update affected project facts. Choose Skills for a specific gap; they are independent capabilities, not required phases.
- Use each Skill's domain method to decide what matters, what evidence supports a choice, and when to adjust or stop. Methodological value should improve the work; it does not require every deliverable to explain a methodology.
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 Changed · +2 lines · +464 tokens per session b7c42ebe6574
- 8d ago Changed · +6 lines · +209 tokens per session c78de60df64e
- 9d ago Changed · +39 lines · +1,631 tokens per session f1aec9c930e5
- 1mo ago Changed · +1 lines · +73 tokens per session 40ee6f8ee7ba
- 1mo ago Changed · -40 lines · -720 tokens per session be47b72c0fc8
- 2mo ago First seen · 131 lines · 2,360 tokens per session scan A f13bdbcb0364
hello-scholar AGENTS.md is an instructions file published in the GitHub repository Tx1207/hello-scholar (10 stars, last pushed 4d ago), licensed MIT. It adds 4,017 tokens to every session, about $0.0161 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-31.
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).
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.
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).
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 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).
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.