speclock: Instructions file for Codex

AGENTS.md

speclock AGENTS.md is an instructions file for Codex, OpenCode from sgroy10/speclock. It costs 262 tokens per session, scanned A, original, MIT.

Development instructions for SpecLock, a Node.js tool that checks planned actions against rules and can connect to coding tools through MCP, a shared tool interface.

In plain words
What is it for?
Checking planned changes, running tests, updating versions, handling hook input safely, and keeping support for Claude Code, Cursor, Windsurf, Cline, Codex, and other MCP clients.
Why use it?
They help maintain the tool's safety rules, compatibility, tests, versions, and public command interfaces while preventing unauthorized releases or data leaks.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/sgroy10/speclock/agents-md"><img src="https://agentmods.dev/badge/instructions/sgroy10/speclock/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 262 This file is loaded in full into every session.
When invoked 262 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.00262 $0.00262
Opus 5.5 $0.00105 $0.00105
Sonnet 5.5 $0.00052 $0.00052
Haiku 4.5 $0.00026 $0.00026

Measured 1mo ago against content hash 70d32b65ef3d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

speclock 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 1mo 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 · 32 lines

What it actually says

SpecLock Development Guide

Project

SpecLock is an MIT-licensed Node.js AI constraint engine. Keep changes focused, preserve the public CLI and MCP APIs, and do not weaken enforcement behavior.

Required checks

  • Run npx speclock check "<planned action>" before changing code.
  • Run npm test before proposing a release.
  • Changes under src/ require a version bump in every location documented in CLAUDE.md. Documentation, metadata, tests, and plugin packaging do not.
  • Never publish, deploy, tag, push, or create a pull request without explicit maintainer approval.

Security

  • Do not commit credentials, deployment identifiers, customer data, or rules copied from another project.
  • Claude Code hook handlers must parse JSON from stdin, cap untrusted input sizes, and fail open on internal errors.
  • Hard enforcement may deny an action only when SpecLock itself reports a blocked conflict. Advisory conflicts must remain warnings.

Compatibility

  • Node.js 18 and later are supported.
  • Keep the local stdio MCP server compatible with Claude Code, Cursor, Windsurf, Cline, Codex, and other MCP clients.
  • Use current official Claude Code plugin and hook schemas.
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. 1mo ago First seen · 32 lines · 262 tokens per session scan A 70d32b65ef3d

Subscribe to this mod's changes

speclock AGENTS.md is an instructions file published in the GitHub repository sgroy10/speclock (25 stars, last pushed 2mo ago), licensed MIT. It adds 262 tokens to every session, about $0.0010 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.