What is stardrive AGENTS.md?

Repository instructions for AI coding agents working on Stardrive, an Astro web project. They require checking whether the repository has been initialized and following its setup files before handling other requests.

Use them when working in Stardrive to check initialization, follow the project’s setup instructions, create its mode marker when required, and then continue with development work.

They prevent an agent from changing an uninitialized project before its required setup and operating mode have been established.

How peltmonger/stardrive configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to peltmonger/stardrive. 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/peltmonger/stardrive/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/peltmonger/stardrive

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/peltmonger/stardrive/agents-md/github.svg)](https://agentmods.dev/instructions/peltmonger/stardrive/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/peltmonger/stardrive/agents-md"><img src="https://agentmods.dev/badge/instructions/peltmonger/stardrive/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/peltmonger/stardrive/agents-md"><img src="https://agentmods.dev/badge/instructions/peltmonger/stardrive/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,838 This file is loaded in full into every session.

When invoked 2,838 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.

Model	Per session	Once invoked
Fable 5.1	$0.02838	$0.02838
Opus 5.5	$0.01135	$0.01135
Sonnet 5.5	$0.00568	$0.00568
Haiku 4.5	$0.00284	$0.00284

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

Security

Grade A, and why

stardrive 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 23d 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 · 134 lines

How it starts

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

🛑 CRITICAL: REPOSITORY BOOTSTRAP DIRECTIVE 🛑

As an AI agent operating in this repository, you MUST execute the following state check before analyzing, coding, or responding to any user prompt:

CHECK STATE: Silently verify if the file STARDRIVE_AGENT_MODE.md exists in the root directory.
IF MISSING (UNINITIALIZED):
- Intercept the prompt: Acknowledge to the user that you are running the initial repository setup first.
- Never (!) proceed without this file being present!
- Read the file SETUP.md in the./.ai/ directory..
- Execute ALL setup, scaffolding, and configuration instructions defined in SETUP.md and related files. Ask the user about clarification where necessary.
- Create the STARDRIVE_AGENT_MODE.md file in the root directory to mark initialization as complete, setting its content to "project" or "boilerplate" - depending on what the user's case is about.
- Proceed to fulfill the user's original request.
IF PRESENT (INITIALIZED):
- Directly proceed to fulfilling the user's prompt.
- Mind the content of the STARDRIVE_AGENT_MODE.md as it defines your general scope as described in the AGENTS.md.

General information and guidelines for AI agents

Analyze your high-level use case first

Check for an STARDRIVE_AGENT_MODE.md file at the root level. Its content is a single keyword that selects your mode:

boilerplate - You are maintaining the boilerplate code itself as a contributor (not building a new website with it). Follow BOILERPLATE_MODE.md. Do not execute the other .ai guides as setup steps (SETUP.md, CONFIG_GUIDE.md, TRIMMING_GUIDE.md, FAVICON_GUIDE.md); they describe the end-user setup flow. You may still read and update them when your changes affect that flow - keeping them accurate is part of boilerplate maintenance.
project - You are using the boilerplate to build a new project and website. Treat this codebase as an already-started project to adjust and extend to the user's specifications, not as a boilerplate. Open PLAN.md first to see what is still open. If no PLAN.md exists yet, the configuration has not been planned - run SETUP.md to create it. Ignore BOILERPLATE_MODE.md.

Read the full file on GitHub · 134 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.

23d ago Changed · +9 lines · +131 tokens per session bacf14f78b10
2mo ago First seen · 125 lines · 2,707 tokens per session scan A 2d179f9d114f

Subscribe to this mod's changes

stardrive AGENTS.md is an instructions file published in the GitHub repository peltmonger/stardrive (216 stars, last pushed 5d ago), licensed MIT. It adds 2,838 tokens to every session, about $0.0114 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.

TypeScript astro astrojs astrojs-boilerplate astrojs-template javascript

stardrive AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
stardrive AGENTS.mdpeltmonger/stardrive	Instructions file	216	5d ago	MIT	A	2,838	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	today	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

stardrive: Instructions file for Codex