Config AGENTS.md

Repository instructions for the Nivl/Config project, covering what the project is, its layout, startup process, and how to keep the instructions current.

In plain words
What is it for?
Use them when exploring, bootstrapping, or modifying the Nivl/Config repository.
Why use it?
They give an agent the project context and operating rules it needs before changing the code.

Instructions file for CodexOpenCode

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/nivl/config/agents-md
Clone the repo
git clone --depth 1 https://github.com/Nivl/Config

Made for: Codex, OpenCode.

Per session 9,261 This file is loaded in full into every session.
When invoked 9,261 The same file — it is already loaded in full.
Security scan C 3 findings. Scan, not verified.
Origin unknown 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.09261 $0.09261
Opus 5 $0.04630 $0.04630
Sonnet 5 $0.01852 $0.01852
Haiku 4.5 $0.00926 $0.00926

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

Security

Grade C, and why

Config AGENTS.md scanned grade C with 3 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

| `internal/claude/perms` | Mutates `permissions.{allow,ask,deny}` in `shared_config/.claude/settings.json` for the `melvin-config claude perms` command. `Variants(kind, value)` fans a value out into rule strings (a `--b

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

- `linkedDirs` (currently just `skills`) goes through `internal/claude/sync/linkdir.go` (`LinkDirEntries`). Each **top-level entry** of `<RepoDir>/skills` becomes its own symlink at `~/.claude/skills/<entry>`, so editing

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| `README.md` | The curl-bootstrap one-liner and its `--dry-run` sibling. |
AGENTS.md · 220 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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 · 220 lines · 9,261 tokens per session scan C f81df6dd754b

Subscribe to this mod's changes

Config AGENTS.md is an instructions file published in the GitHub repository Nivl/Config (2 stars, last pushed 3d ago), with no licence file. It adds 9,261 tokens to every session, about $0.0463 per session on Opus 5. A static security scan graded it C with 3 findings (reads agent configuration directories, enumerates other installed skills, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

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