agentmods.dev

peterroelants.github.io AGENTS.md

Repository-specific instructions for maintaining a personal technical blog built with Jekyll and published through GitHub Pages.

In plain words
What is it for?
Use them when changing blog posts, notebook-derived content, conversion scripts, site architecture, or build-related files in the repository.
Why use it?
They tell coding agents which documentation and source files to read before editing, helping preserve the site’s established structure and editing rules.

Instructions file for CodexOpenCode

349 8d ago A scan 595 tokens original MPL-2.0
View the source file peterroelants/peterroelants.github.io
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/peterroelants/peterroelants.github.io/agents-md
Clone the repo
git clone --depth 1 https://github.com/peterroelants/peterroelants.github.io

Made for: Codex, OpenCode.

Per session 595 This file is loaded in full into every session.
When invoked 595 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.00595 $0.00595
Opus 5 $0.00298 $0.00298
Sonnet 5 $0.00119 $0.00119
Haiku 4.5 $0.00060 $0.00060

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

Security

Grade A, and why

peterroelants.github.io 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 3d 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 · 60 lines

How it starts

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

AGENTS.md

This repository is Peter Roelants' personal technical blog published at https://peterroelants.github.io/. It is a Jekyll/GitHub Pages site with notebook-derived posts, handwritten Markdown posts, and checked-in static assets.

Responsibility: this file is the agent-specific operating guide. It should point agents to the right source documents and capture agent behavior that does not belong in the human-facing README or architecture notes.

Start Here

  • Read README.md for the canonical project overview and navigation to deeper docs.
  • Read build_info/site_overview.md for detailed architecture and site behavior.
  • Read build_info/jekyll.md for Jekyll/GitHub Pages command details.
  • Read notebooks/README.md before changing notebook-derived posts or conversion scripts.
  • Keep this file as the agent-specific overlay. Do not duplicate details from those docs here; update the source doc instead.

Agent Operating Notes

  • Before changing a subsystem, read the relevant section of build_info/site_overview.md and inspect nearby files for the current pattern.
  • Prefer source-of-truth edits. For notebook-derived posts, that usually means editing the source notebook or conversion workflow rather than large manual edits to generated HTML.
  • If the public site mechanics or notebook workflow changes, consider whether _posts/2021/05/2021-05-15-about-this-blog.md also needs an update.
  • When making a substantive change to an existing post, consider whether it needs an updates front matter entry as described in build_info/site_overview.md.
  • Use the Ruby version pinned in .ruby-version. If Bundler is unavailable, install the needed Bundler version rather than rewriting dependency metadata, unless the user explicitly asks for a dependency update.
  • Respect .gitignore; do not commit generated site output, dependency directories, or local caches.

Verification

  • Use command details from build_info/jekyll.md and behavior-specific context from build_info/site_overview.md.
  • Prefer just recipes for standard setup, check, build, serve, and verification flows when just is available.
  • Choose verification based on the change: build checks for templates/content, browser checks for layout or styling, and targeted page checks for affected post, tag, or notebook behavior.
  • If a required check cannot run because local tooling is missing, state the exact command attempted and the error.

Read the full file on GitHub · 60 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. 3d ago First seen · 60 lines · 595 tokens per session scan A 7f1a8003036e

Subscribe to this mod's changes

peterroelants.github.io AGENTS.md is an instructions file published in the GitHub repository peterroelants/peterroelants.github.io (349 stars, last pushed 8d ago), licensed MPL-2.0. It adds 595 tokens to every session, about $0.0030 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.

Writing and docs
Related

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

microsoft/vscode · 6,785 tokens

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

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