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.
npx agentmods add instructions/container-registry/harbor-next/agents-mdgit clone --depth 1 https://github.com/container-registry/harbor-nextWrote 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/container-registry/harbor-next/agents-md)<a href="https://agentmods.dev/instructions/container-registry/harbor-next/agents-md"><img src="https://agentmods.dev/badge/instructions/container-registry/harbor-next/agents-md.svg" alt="Measured on agentmods" 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 | $0.00543 | $0.00543 |
| Opus 5 | $0.00271 | $0.00271 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
harbor-next 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harbor Next Agent Notes
Enhanced fork of goharbor/harbor. Go backend in src/, Angular frontend in src/portal/, build automation via Taskfile.
Commands
task build # Build Go binaries
task test:quick # API lint + unit tests
task test:ci # Full CI pipeline
task images # Build/push Docker images
task dev:up # Local dev with hot reload
task apply-patches # Apply branches listed in taskfile/commercial-patches with jj
task release-ready # Verify those patches against a clean clone
Go test/build need generated API first: task build:gen-apis.
PRs
- Branch off
main, never push direct. - Conventional Commits, capitalized subject:
feat: Add Foo,fix: Resolve Bar,upstream: Cherry-Pick Harbor Fix. - DCO sign-off required:
git commit -s. - Squash and merge only; other merge types break release-please.
- No
Co-Authored-Byor AI attribution trailers. - New features (
feat:) must add a## Release Notessection to the PR description. Its prose is extracted and rendered under## Highlightson the GitHub Release.
GitHub Actions
- Self-hosted runners are intentionally minimal. When adding a workflow shell command that calls a CLI or interpreter, explicitly install or set up that tool in the same job before using it. Do not assume runner images or JavaScript action runtimes expose tools on
PATH. - Pin actions by full commit SHA and keep a version comment, matching the existing workflow style.
- If a workflow calls
node, add an explicitactions/setup-nodestep first.
Release-Please
main uses always-bump-minor; VERSION on main tracks the next development release while .release-please-manifest.json tracks the published release. release-X.Y branches use patch-only versioning. ci:, build:, chore:, test: are hidden from release notes.
exclude-paths: changes touching only .github/, docs/, tests/, or taskfile/ don't bump version. Use ci: for CI-only 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.
- yesterday First seen · 43 lines · 543 tokens per session scan A decc80c1941f
harbor-next AGENTS.md is an instructions file published in the GitHub repository container-registry/harbor-next (30 stars, last pushed today), licensed Apache-2.0. It adds 543 tokens to every session, about $0.0027 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-09-03.
Other instructions, from other repositories
openbridge-webcomponents ci-and-release.instructions.md
Instructions for Ocean-Industries-Concept-Lab/openbridge-webcomponents, covering ci and release, your commit type decides whether anything ships, release model, the eight workflows and two script directories, and they are not interchangeable.
google-play-cli AGENTS.md
AGENTS.md instructions for PollyGlot/google-play-cli, covering agents.md : gplay, glossary, commandes, vérifier and les pièges de ce repo.
drift drift-release-mandatory.instructions.md
Nutze diese Kurz-Instruction, wenn schnell geklaert werden muss, ob im Drift-Repo ein manueller Release-Befehl noetig ist. Kurzregel: Conventional Commits verwenden, Release macht CI.
agentsge-1 cicd.instructions.md
CI/CD Pipeline configuration for PyInstaller binary packaging and release workflow.
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.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.