veripower: Instructions file for Codex

AGENTS.md

veripower AGENTS.md is an instructions file for Codex, OpenCode from chipweaver/veripower. It costs 497 tokens per session, scanned A, original, MIT.

A repository instruction document for VeriPower, a shared workflow for integrated-circuit design. It describes which scripts own events, rules, artifacts, scheduling, storage, and sign-off decisions.

In plain words
What is it for?
Use it when working on the VeriPower repository to understand stage inputs, artifact results, event records, authorization, scheduling, and acceptance checks.
Why use it?
Complex workflows can become unsafe when different parts make overlapping decisions or bypass required records. These instructions clarify runtime boundaries and where each kind of state belongs.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/chipweaver/veripower/agents-md"><img src="https://agentmods.dev/badge/instructions/chipweaver/veripower/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 497 This file is loaded in full into every session.
When invoked 497 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.00497 $0.00497
Opus 5.5 $0.00199 $0.00199
Sonnet 5.5 $0.00099 $0.00099
Haiku 4.5 $0.00050 $0.00050

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

Security

Grade A, and why

veripower 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 · 47 lines

How it starts

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

VeriPower

VeriPower is a host-neutral IC design workflow plugin with independent stage skills. This file guides development of the plugin repository. Existing code and documentation are open to correction.

Task references

  • For repository changes, follow CONTRIBUTING.md for development and validation.
  • For scheduling, artifact provenance or acceptance changes, consult the architecture and the framework guide for the runtime model and implementation entry points.
  • For stage changes, inspect skills/<stage>/SKILL.md, its scripts and relevant references together. Shared machine interfaces live in framework/references/schemas/.
  • For installation and platform integration, use README.md and the relevant adapter guide.

Instructions needed to execute an installed skill belong in the skills and adapters, so execution works without this repository's AGENTS.md or the author's session context.

Runtime boundaries

  • framework/scripts/kernel.py owns the module's append-only events.jsonl, dispatch and outcome collection, and records decisions and signoff. Kernel commands, including queries, remove owner-write permission from intent/ to protect source materials from incidental writes.
  • framework/scripts/rules.py declares stage inputs, directory roots and execution placement. These declarations define dependencies and legal repair owners, including the failed stage.
  • skills/design-flow/SKILL.md defines orchestration and applies the task's actual authorization to decisions. Platform adapters provide native tool integration and preserve host permissions.

signoff records acceptance when the task calls for it, after checking current proofs. The record applies to the accepted evidence; readiness alone does not record acceptance.

Stage boundaries

Stages own their workdir artifacts and close through their own CLI; the kernel publishes the outputs declared in each run's result.json. The module's intent/ tree contains the original requirements and referenced authorities used to resolve discrepancies in derived documents.

Read the full file on GitHub · 47 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 Changed · +5 lines · +27 tokens per session facec4aed042
  2. 13d ago First seen · 42 lines · 470 tokens per session scan A a6d651d383e3

Subscribe to this mod's changes

veripower AGENTS.md is an instructions file published in the GitHub repository chipweaver/veripower (10 stars, last pushed 7d ago), licensed MIT. It adds 497 tokens to every session, about $0.0020 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-10-13.

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