agentmods.dev

borderlint AGENTS.md

A repository rulebook for building software from written specifications. It requires each change to be described, planned, and broken into tasks before code is written.

In plain words
What is it for?
Use it to capture requirements, create task lists, prepare proposals, and guide agents through a fixed development workflow.
Why use it?
It prevents coding from starting with unclear requirements and keeps work traceable from the original request through to the final change.

Instructions file for CodexOpenCode

7 +1 9d ago A scan 1,689 tokens original MIT
View the source file iolairus/borderlint
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/iolairus/borderlint/agents-md
Clone the repo
git clone --depth 1 https://github.com/iolairus/borderlint

Made for: Codex, OpenCode.

Per session 1,689 This file is loaded in full into every session.
When invoked 1,689 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.01689 $0.01689
Opus 5 $0.00844 $0.00844
Sonnet 5 $0.00338 $0.00338
Haiku 4.5 $0.00169 $0.00169

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

Security

Grade A, and why

borderlint 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 · 66 lines

How it starts

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

Agent Instructions — Spec-Driven Development with OpenSpec

This repository follows spec-driven development: no code is written until the change is captured as an OpenSpec proposal with specs, design, and tasks. OpenSpec is the machinery that enforces this; opencode is the agent that executes it.

The golden rule

Spec → Plan → Code. Never skip a stage.

If a request arrives as "build X" and there is no OpenSpec change for it, your first move is /opsx:propose — not writing code.

Workflow

The full pipeline runs from requirements to merge. Stages 0–1 are optional for trivial changes; stages 2–6 are mandatory.

  1. Discover — /req-capture <topic> interviews the user and writes backlog/discovery/<topic>.md. No invented answers: unknowns go to Open questions.
  2. Tasks — /task-generate <topic> slices the discovery into tasks under backlog/tasks/. Alternative entries: /task-import <key> normalizes an existing Jira ticket (pasted by the user) into the backlog; /task-new <title> creates a single task without a discovery doc. Task IDs ARE Jira keys (<project_key>-<n>, provided by the user; -Dnn drafts until the issue exists). /task-enrich <id> adds edge cases, estimates, and unhappy paths; /review-task <id> audits; /task-jira <id> exports Jira wiki markup to backlog/exports/jira/ (not needed for imported tickets).
  3. Propose — /opsx:propose <change-name> creates openspec/changes/<name>/ with proposal, delta specs, design, and tasks. If the change implements a backlog task, the proposal references its ID and the task frontmatter gets change: <name>.
  4. Specify & plan — Delta specs (requirements + GIVEN/WHEN/THEN) as ADDED/MODIFIED/REMOVED; design.md for the approach; tasks.md for checkable steps.
  5. Review — /review-change <name> audits the change before implementation.
  6. Implement — /opsx:apply. Branch gate (mandatory, BEFORE writing any code): check the current branch first. Never implement on main. With work_mode: feature, create and switch to the feature branch (naming rule below) before touching any file. With work_mode: flexible, ask the user where to implement — feature branch (recommended) or directly on the integration branch — and create/switch accordingly before the first edit. Then commit with /git-commit: conventional commits whose footer traces Change:/Task: (tasks.md step)/Jira: (backlog task id).
  7. Deliver — feature branch: /pr-open creates the PR against the integration branch, /ship validates, archives, merges and closes the backlog task. Integration branch: skip /pr-open; /ship validates, archives and pushes (no PR, no review).

Read the full file on GitHub · 66 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 · 66 lines · 1,689 tokens per session scan A cf3fdd815ed0

Subscribe to this mod's changes

borderlint AGENTS.md is an instructions file published in the GitHub repository iolairus/borderlint (7 stars, last pushed 9d ago), licensed MIT. It adds 1,689 tokens to every session, about $0.0084 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-31.

PlanningProductivity
Related

Other instructions, from other repositories

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

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).

microsoft/vscode · 6,785 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens