agentmods.dev

opensrc AGENTS.md

Repository instructions for OpenSrc, a Turborepo monorepo containing a Rust command-line tool and a Next.js documentation site. A monorepo keeps multiple related projects in one repository.

In plain words
What is it for?
Use it when working on the Rust CLI, the documentation site, or a release. It lists development, build, test, format, lint, and release commands.
Why use it?
It tells coding agents where the main parts of the project live and which commands maintainers use. This reduces confusion when building, testing, formatting, linting, or releasing.

Instructions file for CodexOpenCode

3.0k +3 2mo ago A scan 822 tokens original Apache-2.0
View the source file vercel-labs/opensrc
Install

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.

agentmods
npx agentmods add instructions/vercel-labs/opensrc/agents-md
Clone the repo
git clone --depth 1 https://github.com/vercel-labs/opensrc

Made for: Codex, OpenCode.

Per session 822 This file is loaded in full into every session.
When invoked 822 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00822 $0.00822
Opus 5 $0.00411 $0.00411
Sonnet 5 $0.00164 $0.00164
Haiku 4.5 $0.00082 $0.00082

Measured 2d ago against content hash f735efc8e777, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

opensrc 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 2d 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 · 85 lines

How it starts

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

AGENTS.md

Instructions for AI coding agents working with this codebase.

Monorepo Structure

This is a Turborepo monorepo with pnpm workspaces:

  • packages/opensrc/ — Rust CLI distributed via npm
  • apps/docs/ — Next.js documentation site

CLI (packages/opensrc)

The CLI is a Rust binary with an npm shim. The Rust crate lives in packages/opensrc/cli/.

  • Build: cargo build --manifest-path packages/opensrc/cli/Cargo.toml
  • Test: cargo test --manifest-path packages/opensrc/cli/Cargo.toml
  • Format: cargo fmt --manifest-path packages/opensrc/cli/Cargo.toml
  • Lint: cargo clippy --manifest-path packages/opensrc/cli/Cargo.toml -- -D warnings
  • Release build + copy to bin/: cd packages/opensrc && npm run build:native

Docs (apps/docs)

  • Dev: cd apps/docs && pnpm dev
  • Build: cd apps/docs && pnpm build

Or from root: turbo dev, turbo build

Releasing

Releases are manual, single-PR affairs. The maintainer controls the changelog voice and format.

To prepare a release:

  1. Create a branch (e.g. prepare-v0.7.0)
  2. Bump version in packages/opensrc/package.json
  3. Run cd packages/opensrc && npm run version:sync to update cli/Cargo.toml and cli/Cargo.lock
  4. Write the changelog entry in CHANGELOG.md at the top, under a new ## <version> heading, wrapped in <!-- release:start --> and <!-- release:end --> markers. Remove the markers from the previous release entry so only the new release has markers.
  5. Open a PR and merge to main

When the PR merges, CI compares packages/opensrc/package.json version to what's on npm. If it differs, it builds all 7 platform binaries, publishes to npm, and creates the GitHub release automatically. The GitHub release body is extracted from the content between the <!-- release:start --> and <!-- release:end --> markers in CHANGELOG.md.

Writing the changelog

Review the git log since the last release and write the entry in CHANGELOG.md. Follow the existing format and voice. Group changes under ### New Features, ### Bug Fixes, ### Improvements, etc. Bold the feature/fix name, then describe it concisely. Reference PR numbers in parentheses.

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

  1. 2d ago First seen · 85 lines · 822 tokens per session scan A f735efc8e777

Subscribe to this mod's changes

opensrc AGENTS.md is an instructions file published in the GitHub repository vercel-labs/opensrc (2,974 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 822 tokens to every session, about $0.0041 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.

LLMaiai-codingclicoding-agentsdeveloper-tools
Related

Other instructions, from other repositories

nanocoder CLAUDE.md

Claude Code instructions for Nano-Collective/nanocoder, covering claude.md, development commands, build and run, testing (run before committing) and individual test commands.

Nano-Collective/nanocoder · 2,693 tokens

nanocoder AGENTS.md

AGENTS.md instructions for Nano-Collective/nanocoder, covering agents.md, project overview, architecture, key files and development commands.

Nano-Collective/nanocoder · 1,165 tokens

vibe-coding-repository-standard AGENTS.md

Instructions for cz1993/vibe-coding-repository-standard, covering vcrs repository instructions, purpose, communication, change discipline and privacy and safety.

cz1993/vibe-coding-repository-standard · 646 tokens

hunch CLAUDE.md

Instructions for davesheffer/hunch, covering claude.md, what this is, commands, architecture and 🧠 hunch (engineering memory).

davesheffer/hunch · 2,910 tokens

tokenmaxxing AGENTS.md

Instructions for 851-labs/tokenmaxxing, covering repository instructions, effect error style, export style, conventions and cli output style.

851-labs/tokenmaxxing · 438 tokens

hunch copilot-instructions.md

Instructions for davesheffer/hunch, covering copilot instructions, 🧠 hunch (engineering memory) and ⛔ top invariants (do not break).

davesheffer/hunch · 1,510 tokens