specmint-core: Instructions file for Codex

AGENTS.md

specmint-core AGENTS.md is an instructions file for Codex, OpenCode from ngvoicu/specmint-core. It costs 664 tokens per session, scanned A, original, MIT.

A repository instruction file for SpecMint Core, a project for creating structured software specifications. It explains the project layout, specification format, development commands, and how related knowledge is accessed.

In plain words
What is it for?
It helps agents inspect the repository, create or update specification files, run checks, and follow the project’s forge, implementation, and resume workflow.
Why use it?
It gives coding agents the project’s required workflow, naming rules, testing guidance, and architecture context. This helps keep generated specifications and code consistent with the repository.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions subagents; mentions Claude Code; mentions Codex.

This is ngvoicu/specmint-core's own configuration. It tells Codex and OpenCode how to work on specmint-core 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 specmint-core configures →

Reuse

Borrowing it

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

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 specmint-core AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/ngvoicu/specmint-core/agents-md"><img src="https://agentmods.dev/badge/instructions/ngvoicu/specmint-core/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 664 This file is loaded in full into every session.
When invoked 664 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.00664 $0.00664
Opus 5.5 $0.00266 $0.00266
Sonnet 5.5 $0.00133 $0.00133
Haiku 4.5 $0.00066 $0.00066

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

Security

Grade A, and why

specmint-core 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 4d 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 · 38 lines

How it starts

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

Repository Guidelines

For architectural context across the Mint family (core vs TDD, distribution, evals), read and write to the ngvoicu-sme brain through kluris — /kluris-ngvoicu-sme (Claude Code skill: search, learn, remember, create) or kluris search "<query>" --brain ngvoicu-sme (CLI). Never edit brain files by hand.

Project Structure & Module Organization

  • SKILL.md: universal, cross-tool skill instructions (Claude Code, Codex, Cursor, Windsurf, Cline, Gemini CLI) — the full forge/implement/resume workflow.
  • references/researcher.md: deep-research subagent brief, spawned via the tool's subagent/task feature (e.g. Claude Code's Agent tool) during forge.
  • references/spec-format.md: canonical SPEC.md format and markers.
  • references/command-contracts.md: behavioral contract checklist for the skill.
  • skills/specmint-core/SKILL.md: symlink to ../../SKILL.md for skills-CLI discovery (never replace with a real file).
  • .specs/: local dogfooding output for specs (gitignored in this repo).

Build, Test, and Development Commands

  • rg --files: fast inventory of repository files before editing.
  • sed -n '1,160p' SKILL.md: inspect skill content in terminal.
  • npx skills add ngvoicu/specmint-core -g -a codex: smoke-test skill installation flow.
  • git log --oneline -n 10: review recent commit style before committing.

This repository has no compile/build pipeline; Markdown and JSON are consumed directly by host tools.

Coding Style & Naming Conventions

  • Keep content ASCII Markdown/JSON with concise, imperative instructions.
  • Use lowercase, hyphenated filenames for reference docs (for example references/spec-format.md).
  • Keep workflow docs procedural (numbered steps, explicit file paths, deterministic behavior).
  • Follow spec naming in examples: spec IDs are lowercase-hyphenated (user-auth-system), task codes are [AUTH-01], and phase markers use [pending], [in-progress], [completed], [blocked].

Testing Guidelines

  • No automated test suite currently exists in this repository.
  • Perform manual validation for each change:
    • Confirm referenced paths/files exist.
    • Smoke-test the install/use flow in a disposable project when skill behavior changes (e.g. npx skills add ./. -g -a claude-code, or copy SKILL.md into the tool's skills directory, then exercise forge / resume / implement).
  • If you change spec-format rules, update both SKILL.md and references/spec-format.md in the same PR.

Read the full file on GitHub · 38 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. 4d ago Changed · +14 tokens per session 3fb74ce527b4
  2. 1mo ago First seen · 38 lines · 650 tokens per session scan A 97be8d5a37f0

Subscribe to this mod's changes

specmint-core AGENTS.md is an instructions file published in the GitHub repository ngvoicu/specmint-core (12 stars, last pushed 4d ago), licensed MIT. It adds 664 tokens to every session, about $0.0027 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-08-30.

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

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens