Borrowing it
Nothing to install: this file belongs to portolan-sdi/portolan-cli. 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/portolan-sdi/portolan-cli/main/AGENTS.mdgit clone --depth 1 https://github.com/portolan-sdi/portolan-cliWrote 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/portolan-sdi/portolan-cli/agents-md)<a href="https://agentmods.dev/instructions/portolan-sdi/portolan-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/portolan-sdi/portolan-cli/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/portolan-sdi/portolan-cli/agents-md"><img src="https://agentmods.dev/badge/instructions/portolan-sdi/portolan-cli/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.02751 | $0.02751 |
| Opus 5.5 | $0.01100 | $0.01100 |
| Sonnet 5.5 | $0.00550 | $0.00550 |
| Haiku 4.5 | $0.00275 | $0.00275 |
Grade A, and why
portolan-cli 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 yesterday.
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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Portolan agent norms
All agents MUST read this document before starting work, with no exceptions, ever. (Claude Code does not read AGENTS.md but imports this file via a one-line CLAUDE.md.) Most of this content is synced downstream from portolan-ops. Put repo-specific instructions in AGENTS.md, never in CLAUDE.md, which the sync overwrites.
Ground rules
Agents MUST read the complete contents of norms and policies before starting work, with no exceptions, ever.
The portolan-spec repo is the absolute ground truth for the Portolan spec. All other tools are downstream of it.
Before documenting any command, flag, or API, verify that it exists.
Use conventional commits always.
All tickets and PRs MUST follow the templates.
GitHub applies issue forms only in the web UI. With gh issue create, write each form field as a ### <field label> heading, in the form's order. Include ### Priority with one of P0 to P3 from the priority rubric. Pass the form's type label with --label, and pass the body with --body-file. The writing hook denies a body that skips its form, and issue governance flags one.
Org-wide facts
The canonical homepage is https://www.portolan-sdi.org/. Canonical URLs live in copy/urls.md. Do not hardcode variants.
Community discussion happens in the Portolan Google Group and the Portolan channel in Cloud-Native Geo Slack. Planning happens in org-level GitHub projects.
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.
- yesterday Changed · -4 tokens per session 24dbdb2e7822
- 2d ago Changed · +2 lines · +122 tokens per session 54ccc34beb35
- 9d ago Changed · -8 lines · -574 tokens per session 3fcdf09299e6
- 10d ago Changed · -47 lines · -1,276 tokens per session 3675b907808c
- 12d ago Changed · +4 tokens per session 6b0c9517810e
- 13d ago Changed · +2 lines · +49 tokens per session 28cfa2a97b20
- 15d ago Changed 763eb2651ef0
- 19d ago Changed b91b3d3ffc23
- 1mo ago Changed · +2 lines · +143 tokens per session 42f1bd2db9a6
- 1mo ago First seen · 275 lines · 4,287 tokens per session scan A 9154abf5e304
portolan-cli AGENTS.md is an instructions file published in the GitHub repository portolan-sdi/portolan-cli (42 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,751 tokens to every session, about $0.0110 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.