Borrowing it
Nothing to install: this file belongs to PackmindHub/packmind. 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/PackmindHub/packmind/main/AGENTS.mdgit clone --depth 1 https://github.com/PackmindHub/packmindWrote 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/packmindhub/packmind/agents-md)<a href="https://agentmods.dev/instructions/packmindhub/packmind/agents-md"><img src="https://agentmods.dev/badge/instructions/packmindhub/packmind/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/packmindhub/packmind/agents-md"><img src="https://agentmods.dev/badge/instructions/packmindhub/packmind/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.01804 | $0.01804 |
| Opus 5.5 | $0.00722 | $0.00722 |
| Sonnet 5.5 | $0.00361 | $0.00361 |
| Haiku 4.5 | $0.00180 | $0.00180 |
Grade A, and why
packmind 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 1mo 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
_# Nx Monorepo Structure
This is an Nx monorepo containing applications and reusable packages.
Core Technologies
- Runtime: Node.js (version specified in
.nvmrc) - Language: TypeScript
- Database: PostgreSQL with TypeORM for entity persistence
- Cache: Redis for caching
- Background Jobs: BullMQ for job queue management
- Testing: Jest with @swc/jest as test runner. Tests are run with
./node_modules/.bin/nx run <project-name>as detailed below.
Directory Structure
apps/- Deployable applications (API, frontend, CLI, e2e tests, docs)packages/- Reusable domain and infrastructure packages shared across apps.github/workflows/- CI/CD pipelines for build, test, quality checks, and deployment
Local Development Environment
Local development uses Docker Compose to run all services (API, frontend, database, Redis, etc.):
docker compose up
This starts the entire development environment. Docker Compose automatically provisions PostgreSQL and Redis - no manual setup required.
Working with Nx
The following commands apply for both NX apps and packages (use ./node_modules/.bin/nx show projects to list actual apps and packages.)
- Test a project:
./node_modules/.bin/nx test <project-name> - Lint a project:
./node_modules/.bin/nx lint <project-name> - Build a project:
./node_modules/.bin/nx build <project-name> - Test affected projects:
pnpm run test:staged - Lint affected projects:
pnpm run lint:staged
Code Quality
- Linting:
./node_modules/.bin/nx lint <project-name>runs ESLint, using the config fileeslint.config.mjs. - Formatting: Prettier is used for code formatting. You don't have to run it, it's set as a pre-commit hook.
Commands
- When running commands, ensure you use the correct Node version (see .nvmrc at the project's root level)
- When renaming or moving a file that is commited to git, use
git mvinstead ofmv - Ensure the env variable
PACKMIND_EDITIONis properly set tooss
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.
- 1mo ago Changed · +1 lines · +14 tokens per session deacdb583a6a
- 1mo ago Changed · -9 lines · -67 tokens per session 485d3760cd9f
- 1mo ago Changed · +16 lines · +162 tokens per session 76b0f821939a
- 1mo ago First seen · 126 lines · 1,695 tokens per session scan A 9066f4643e00
packmind AGENTS.md is an instructions file published in the GitHub repository PackmindHub/packmind (319 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,804 tokens to every session, about $0.0072 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.
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.