spectre AGENTS.md

spectre AGENTS.md is an instructions file for Codex, OpenCode from joenandez/spectre. It costs 608 tokens per session, scanned A, original, MIT.

Repository guidance for Spectre, a project whose canonical source files are transformed into generated Codex output. It explains which files to edit and which synchronization and verification commands to run.

In plain words
What is it for?
Changing skills, subagents, hooks, installer behavior, or translation rules, then synchronizing and checking the generated Codex files.
Why use it?
It prevents agents from editing generated files directly and helps keep the shipped output consistent with the source.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions subagents; mentions AGENTS.md.

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/joenandez/spectre/agents-md
Clone the repo
git clone --depth 1 https://github.com/joenandez/spectre

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 spectre AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/joenandez/spectre/agents-md.svg)](https://agentmods.dev/instructions/joenandez/spectre/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/joenandez/spectre/agents-md"><img src="https://agentmods.dev/badge/instructions/joenandez/spectre/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 608 This file is loaded in full into every session.
When invoked 608 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.1 $0.00608 $0.00608
Opus 5 $0.00304 $0.00304
Sonnet 5 $0.00122 $0.00122
Haiku 4.5 $0.00061 $0.00061

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

Security

Grade A, and why

spectre 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 6d 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 · 49 lines

How it starts

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

AGENTS.md

Guidance for coding agents working in this repository.

Source Of Truth

  • plugins/spectre/ is the canonical plugin source.
  • plugins/spectre-codex/ is generated Codex output. Do not hand-edit it.
  • After changing canonical skills, agents, hooks, or plugin assets that ship to Codex, run:
    npm run sync-codex -- --quiet
    npm run sync-codex -- --check --quiet
    
  • If generated output is wrong, fix the canonical source or the translator under scripts/; do not patch plugins/spectre-codex/ directly.

Change Workflow

  1. Check git status --short --branch before editing.
  2. Identify the change type:
    • workflow skill: edit plugins/spectre/skills/<skill>/SKILL.md
    • subagent: edit plugins/spectre/agents/*.md
    • learning/runtime helper: edit plugins/spectre/hooks/scripts/*
    • Codex install/update behavior: edit src/ and load the project skill feature-codex-spectre-implementation first
    • translator behavior: edit scripts/translators/* and scripts/sync-codex.cjs
  3. Make changes only in the canonical source tree unless the target is installer or translator code.
  4. Run npm run sync-codex -- --quiet.
  5. Run npm run sync-codex -- --check --quiet.
  6. Run the smallest relevant test command; use npm test when translators, installer behavior, or shared runtime helpers changed.
  7. Review the diff. Generated plugins/spectre-codex/ changes are expected after sync; manual edits there are not.

Skill Editing Rules

  • Keep skills in compact contract form: Purpose, Inputs, Working Set, Outputs + DONE, Method/guardrails, Handoff, Escalate-If.
  • Prefer prompts that call focused prompts over duplicating another skill's body.
  • Keep dynamic data late-bound: branch names, diffs, file lists, and task paths should be read at runtime, not baked into skill text.
  • Preserve load-bearing gates explicitly: scope boundaries, destructive-operation guards, verification postconditions, DONE criteria, and no-suppression rules.
  • For skill rewrites or compression, use the spectre-rewrite-skill guidance as the quality bar before editing.

Read the full file on GitHub · 49 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. 6d ago First seen · 49 lines · 608 tokens per session scan A fcc35de69a0d

Subscribe to this mod's changes

spectre AGENTS.md is an instructions file published in the GitHub repository joenandez/spectre (158 stars, last pushed yesterday), licensed MIT. It adds 608 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.

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

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

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

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

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

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