DevVerse-SWE-Blog: Instructions file for Codex

AGENTS.md

DevVerse-SWE-Blog AGENTS.md is an instructions file for Codex, OpenCode from hoangsonww/DevVerse-SWE-Blog. It costs 750 tokens per session, scanned A, original, MIT.

A repository instruction guide for coding agents working on the DevVerse-SWE-Blog project. It records which files hold article content, which page and styling contracts must stay intact, and how to handle secrets.

In plain words
What is it for?
Use it when changing the blog's articles, routes, layout, dark mode, chat responses, or content and data handling.
Why use it?
It prevents an agent from trusting outdated documentation, breaking linked parts of the site, or exposing secret values while editing the project.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions Codex.

This is hoangsonww/DevVerse-SWE-Blog's own configuration. It tells Codex and OpenCode how to work on DevVerse-SWE-Blog itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything DevVerse-SWE-Blog configures →

Reuse

Borrowing it

Nothing to install: this file belongs to hoangsonww/DevVerse-SWE-Blog. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/hoangsonww/DevVerse-SWE-Blog/master/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/hoangsonww/DevVerse-SWE-Blog

Made for: Codex, OpenCode.

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

agentmods badge for DevVerse-SWE-Blog AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/hoangsonww/devverse-swe-blog/agents-md/github.svg)](https://agentmods.dev/instructions/hoangsonww/devverse-swe-blog/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/hoangsonww/devverse-swe-blog/agents-md"><img src="https://agentmods.dev/badge/instructions/hoangsonww/devverse-swe-blog/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.

agentmods 80×15 button for DevVerse-SWE-Blog AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/hoangsonww/devverse-swe-blog/agents-md"><img src="https://agentmods.dev/badge/instructions/hoangsonww/devverse-swe-blog/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 750 This file is loaded in full into every session.
When invoked 750 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00750 $0.00750
Opus 5.5 $0.00300 $0.00300
Sonnet 5.5 $0.00150 $0.00150
Haiku 4.5 $0.00075 $0.00075

Measured 1mo ago against content hash 3a8b078c6f3e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

DevVerse-SWE-Blog 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.

AGENTS.md · 71 lines

How it starts

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

DevVerse Codex Guidance

Core Expectations

  • Treat content/*.mdx as the canonical article store. The SQL article schemas in supabase/ are not the runtime source of article content.
  • Prefer code over README when they conflict. Parts of the README are stale.
  • Keep changes narrow. This repo has duplicated article parsers and several UI/data contracts that are easy to break with broad refactors.
  • Do not read or print real secret values from .env or .env.*. Use .env.example for variable names and expected configuration.
  • Use rg and rg --files for search.

Architecture Invariants

  • Preserve the split between / and /home.
  • / is the landing page and intentionally hides the navbar.
  • /home is the article browser.
  • Preserve .mdx-container and the h2 / h3 article heading structure. components/TableOfContents.tsx depends on both.
  • Preserve the dark-mode chain across:
    • the inline boot script in app/layout.tsx
    • the dark class on <html>
    • CSS variables in app/globals.css
    • provider/DarkModeProvider.tsx
  • Preserve the chat response contract across app/chat/page.tsx, lib/chat-citations.ts, and lib/rag.ts.
    • assistant answers use bracket citations
    • backend appends a trailing Sources: section
    • UI strips that section and links citations to message.sources

MDX Content Contract

  • Keep article metadata as a literal export const metadata = { ... };.
  • Keep title, description, and topics as literal string/array fields.
  • Keep ### Author: ....
  • Keep > Date: YYYY-MM-DD.
  • Keep article body starting with a top-level # heading.
  • If you change that contract, update all dependent parsers together:
    • lib/rss.ts
    • lib/rag-local.ts
    • scripts/vectorize_articles.mjs
    • any affected tests

Security Boundaries

  • Keep SUPABASE_SERVICE_ROLE_KEY server-only.
  • Treat these routes as security-sensitive:
    • app/api/verify-email/route.ts
    • app/api/reset-password/route.ts
  • Do not move service-role Supabase code into shared modules imported by client code.

Read the full file on GitHub · 71 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. 1mo ago First seen · 71 lines · 750 tokens per session scan A 3a8b078c6f3e

Subscribe to this mod's changes

DevVerse-SWE-Blog AGENTS.md is an instructions file published in the GitHub repository hoangsonww/DevVerse-SWE-Blog (15 stars, last pushed 1mo ago), licensed MIT. It adds 750 tokens to every session, about $0.0030 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-09-04.

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 · 9,715 tokens

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.

vercel/next.js · 7,461 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

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

microsoft/vscode · 2,731 tokens

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.

denoland/deno · 3,077 tokens