speky: Instructions file for Codex

AGENTS.md

speky AGENTS.md is an instructions file for Codex, OpenCode from agagniere/speky. It costs 1,266 tokens per session, scanned A, original, MIT.

A project guide for Speky, a Python tool that stores project requirements and tests in YAML or TOML files and generates documentation and PDFs.

In plain words
What is it for?
Use it to maintain version-controlled specifications, run their tests, create HTML or PDF documentation, and provide specs to AI assistants.
Why use it?
It explains how to install, test, format, validate specifications, generate documentation, and expose those specifications to AI agents through MCP.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/agagniere/speky/agents-md"><img src="https://agentmods.dev/badge/instructions/agagniere/speky/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,266 This file is loaded in full into every session.
When invoked 1,266 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.01266 $0.01266
Opus 5.5 $0.00506 $0.00506
Sonnet 5.5 $0.00253 $0.00253
Haiku 4.5 $0.00127 $0.00127

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

Security

Grade A, and why

speky 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 · 100 lines

How it starts

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

AGENTS.md

This file provides guidance to AI coding agents when working with code in this repository.

Project Overview

Speky is a Python tool for writing project specifications (requirements and tests) in YAML or TOML, version-controlled alongside code. It generates static HTML (via Sphinx/MyST) and PDFs (via Typst), and exposes specs to LLM agents via an MCP server.

Commands

Setup:

uv sync

Run all tests:

uv run pytest --import-mode importlib --quiet

Run a single test:

uv run pytest --import-mode importlib tests/test_mcp_server.py::TestInitialization::test_initialize -v

Format and lint:

uv run --dev ruff format python tests
uv run --dev ruff check python tests
uv run --dev ruff check --fix python tests

Validate YAML specs:

make -C specs check

Generate Markdown and HTML from specs:

uv run speky specs/speky.yaml --output-folder markdown
uv run --with furo,sphinx-design,sphinx-copybutton,myst-parser sphinx-build -M html markdown output --conf-dir .

Sphinx's conf.py must set project, include 'substitution' in myst_enable_extensions, and set myst_substitutions = {'project': project}.

Architecture

The project has two Python packages under python/:

speky — CLI tool

  • main.py — Argument parsing and orchestration
  • specification.py — Loads YAML/TOML files and kind: project manifests, resolves cross-references, scans source code for speky:<project>#<ID> tags, computes test-plan coverage
  • models.py — Requirement, Test, Comment, Manifest, SourceLinkConfig data models
  • scanner.py — Tree-sitter based scanner extracting code references from Python/Go/Rust/Bash sources
  • generators/markdown.py — MyST Markdown output
  • utils.py, log_formatter.py — Field-import helpers and CLI log formatting
  • assets/ — Default logging.yaml config and speky.css copied into the generated Markdown folder

speky_mcp — MCP server

Exposes specs over JSON-RPC 2.0 to LLM clients (e.g., Claude).

  • server.py — Startup, initialization, request dispatch
  • tools.py — Tool implementations (search, get, list operations)
  • protocol.py — JSON-RPC error types

Read the full file on GitHub · 100 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. 1mo ago First seen · 100 lines · 1,266 tokens per session scan A 6e8f7dd418e3

Subscribe to this mod's changes

speky AGENTS.md is an instructions file published in the GitHub repository agagniere/speky (2 stars, last pushed 5mo ago), licensed MIT. It adds 1,266 tokens to every session, about $0.0051 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-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 · 9,649 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,384 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,159 tokens