Borrowing it
Nothing to install: this file belongs to amalshaji/agent-thread. 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/amalshaji/agent-thread/main/AGENTS.mdgit clone --depth 1 https://github.com/amalshaji/agent-threadWrote 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/amalshaji/agent-thread/agents-md)<a href="https://agentmods.dev/instructions/amalshaji/agent-thread/agents-md"><img src="https://agentmods.dev/badge/instructions/amalshaji/agent-thread/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/amalshaji/agent-thread/agents-md"><img src="https://agentmods.dev/badge/instructions/amalshaji/agent-thread/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.00694 | $0.00694 |
| Opus 5.5 | $0.00278 | $0.00278 |
| Sonnet 5.5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
agent-thread 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This repository is a Bun-managed Next.js/OpenNext app. Use Bun for project commands and dependency management, and keep changes aligned with the existing Next.js App Router and Cloudflare Worker deployment path.
Tooling
- Use
bun installinstead ofnpm install,yarn install, orpnpm install. - Use
bun run <script>instead ofnpm run <script>,yarn run <script>, orpnpm run <script>. - Use
bun testfor tests. - Use
bunx <package> <command>instead ofnpx <package> <command>. - Do not introduce Vite, Express, Jest, Vitest, npm, yarn, or pnpm.
- When a dependency exposes a Node-oriented CLI, invoke it through Bun, matching the existing scripts. For example:
bun --bun ./node_modules/next/dist/bin/next build. - Codex or editor host tooling may use its own configured Node runtime when that tool requires it, such as
js_replor browser automation. That exception does not justify adding Node setup, npm scripts, or a project-level Node workflow.
Project Commands
- Install dependencies:
bun install - Run the Next.js dev server:
bun run dev - Build the app and CLI:
bun run build - Build only the CLI:
bun run build:cli - Preview the Cloudflare Worker:
bun run preview - Deploy through OpenNext/Cloudflare:
bun run deploy - Type-check:
bun run check - Run tests:
bun test - Run the local CLI entrypoint:
bun run cli
Release Workflow
- When updating the CLI version, title the pull request
Release cli {version}, replacing{version}with the exact version being released.
Architecture
- The frontend and API routes live in Next.js App Router.
- The Cloudflare Worker is produced by
@opennextjs/cloudflare;wrangler.tomlpoints at.open-next/worker.js. - Keep
next.config.tscompatible with the OpenNext build path, includingoutput: "standalone", unless the deployment strategy is intentionally changed. - Keep server-side rendering and public transcript rendering in the Next app rather than reintroducing a separate Bun.serve frontend.
- Keep Cloudflare bindings and runtime-specific code isolated behind the existing helper modules.
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.
- 2mo ago First seen · 56 lines · 694 tokens per session scan A 226ad11ed810
agent-thread AGENTS.md is an instructions file published in the GitHub repository amalshaji/agent-thread (1 stars, last pushed 5mo ago), licensed MIT. It adds 694 tokens to every session, about $0.0028 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.