llm-wiki-newsroom: Instructions file for Codex

AGENTS.md

llm-wiki-newsroom AGENTS.md is an instructions file for Codex, OpenCode from alfadur7/llm-wiki-newsroom. It costs 1,675 tokens per session, scanned A, original, MIT.

Legacy workflow instructions for an LLM Wiki Newsroom, a project that builds a searchable wiki and source catalogue from researched material. They explain which files are generated, which scripts build and check them, and how names and person records should be handled.

In plain words
What is it for?
Use them when maintaining the newsroom wiki, source catalogue, graph files, generated indexes, naming conventions, or the build and lint workflow.
Why use it?
They prevent manual edits to generated files and require the project's build and lint checks before content is treated as published. They also preserve rules for source-backed person records and file naming.

Instructions file for CodexOpenCode

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

This is alfadur7/llm-wiki-newsroom's own configuration. It tells Codex and OpenCode how to work on llm-wiki-newsroom 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 llm-wiki-newsroom configures →

Reuse

Borrowing it

Nothing to install: this file belongs to alfadur7/llm-wiki-newsroom. 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/alfadur7/llm-wiki-newsroom/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/alfadur7/llm-wiki-newsroom

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 llm-wiki-newsroom AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/alfadur7/llm-wiki-newsroom/agents-md/github.svg)](https://agentmods.dev/instructions/alfadur7/llm-wiki-newsroom/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/alfadur7/llm-wiki-newsroom/agents-md"><img src="https://agentmods.dev/badge/instructions/alfadur7/llm-wiki-newsroom/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 llm-wiki-newsroom AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/alfadur7/llm-wiki-newsroom/agents-md"><img src="https://agentmods.dev/badge/instructions/alfadur7/llm-wiki-newsroom/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,675 This file is loaded in full into every session.
When invoked 1,675 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.01675 $0.01675
Opus 5 $0.00838 $0.00838
Sonnet 5 $0.00335 $0.00335
Haiku 4.5 $0.00168 $0.00168

Measured 11d ago against content hash 9d939493e723, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

llm-wiki-newsroom 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 11d 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 · 201 lines

How it starts

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

LLM Wiki Newsroom — Schema & Workflow Instructions

⚠️ LEGACY COMPATIBILITY MODE — read this first. This file describes the original "no scripts" workflow and has drifted from the current architecture. The source of truth is CLAUDE.md + .claude/ (5-role multi-agent flow, 9 slash commands, deterministic tools/ pipeline). Even in this minimal mode, four rules are non-negotiable:

  1. Never hand-edit generated artifacts: wiki/index.md, wiki/sources/_catalog*.md, any <!-- AUTO:* BEGIN/END --> region, or anything under graph/ — run python tools/build.py instead.
  2. Never hand-write graph/graph.html or graph/*.json — the HTML is a committed Sigma.js shell that fetches build artifacts.
  3. Run python tools/lint.py and require exit 0 before treating content as published.
  4. English TitleCase filenames are the default; non-Latin-script entities may use a native-script filename (e.g. 신한은행.md) — .claude/policies/naming.md; new person stubs need ≥3 distinct citing sources + operator approval.

This repo can be driven conversationally by any coding agent, but the deterministic tools/ scripts (stdlib + a few pip deps, no API key) are required for build/lint — they are not optional.

How to Use

Describe what you want in plain English:

  • "Ingest this file: raw/papers/my-paper.md"
  • "What does the wiki say about transformer models?"
  • "Check the wiki for orphan pages and contradictions"
  • "Build the knowledge graph"

Or use shorthand triggers:

  • ingest <file> → runs the Ingest Workflow
  • query: <question> → runs the Query Workflow
  • lint → runs the Lint Workflow
  • build graph → runs the Graph Workflow

Directory Layout

raw/          # Immutable source documents — never modify these
wiki/         # Agent owns this layer entirely
  index.md    # Catalog of all pages — generated by `python tools/build.py index`
  overview.md # Living synthesis across all sources
  sources/    # One summary page per source document
  entities/   # People, companies, projects, products
  concepts/   # Ideas, frameworks, methods, theories
  overviews/  # L2-3 cluster landscape overviews
  contradictions/ # L2-3 conflict-axis theme pages
  syntheses/  # Saved query answers
  timelines/  # Chronological hub pages
  trails/     # Associative trails (Memex)
graph/        # Auto-generated graph data (build.py output — do not hand-edit)
tools/        # Optional standalone Python scripts (no API key required)
log.md        # Append-only chronological record (repo root, not under wiki/)

Read the full file on GitHub · 201 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. 11d ago First seen · 201 lines · 1,675 tokens per session scan A 9d939493e723

Subscribe to this mod's changes

llm-wiki-newsroom AGENTS.md is an instructions file published in the GitHub repository alfadur7/llm-wiki-newsroom (85 stars, last pushed 2d ago), licensed MIT. It adds 1,675 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-30.

Related

Other instructions, from other repositories

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,296 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,153 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

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

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,469 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