spacedock: Instructions file for Codex

AGENTS.md

spacedock AGENTS.md is an instructions file for Codex, OpenCode from spacedock-dev/spacedock. It costs 500 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for spacedock, a Go-based launcher and its project-side skill integration.

In plain words
What is it for?
Use them when changing spacedock, running its required checks, organizing packages, or preparing a versioned release.
Why use it?
They define coding priorities, expected tests and formatting, project structure, and rules for stable releases.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

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

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

Security

Grade A, and why

spacedock 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 · 50 lines

How it starts

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

Agent Instructions

This repo builds the Go-based spacedock launcher and the project-side skill integration behind its stable command surface.

Priorities

  • Prefer small Go packages with clear boundaries. Avoid a single large CLI file.
  • Use the standard library unless a dependency removes real complexity.
  • Keep command output stable and test it with fixtures.

Expected Commands

Run these before claiming work is complete:

go test ./...
go test ./... -race
gofmt -w ./cmd ./internal

Add focused tests for each stage before implementing that stage.

Releasing

Cut stable releases from main via an annotated vX.Y.Z tag — see docs/releasing.md. next is a dev-only source-build convenience branch (go install …@next, --plugin-dir) — the edge marketplace entry resolves main directly, so next is not a re-pull source for any installer. Do not cut a stable vX.Y.Z tag from it.

Project Shape

  • cmd/spacedock/: process entry point only.
  • internal/cli/: command routing, usage text, exit-code behavior.
  • internal/status/: status implementation.
  • docs/specs/: design contracts, including the state behavior extension.
  • docs/roadmap/: bootstrap and migration roadmap.
  • docs/dev/README.md: development workflow definition.
  • docs/dev/.spacedock-state/: development workflow entities in a separate state checkout.
  • skills/: first-officer, ensign, and satellite skills plus integration fixtures.

Skill Development

  • Skills should call spacedock, not plugin-private script paths.
  • Keep skill instructions declarative. Let the binary own path resolution and mutation guards.
  • Add skill smoke tests before changing first-officer or ensign command text.
  • Preserve current FO/ensign write-scope rules: the first officer mutates entity state; ensigns write assigned code, reports, and artifacts.

Runtime Support

  • When adding a new runtime host or debugging first-contact runtime friction, read docs/runtime-support.md first.
  • Use the documented "assume it already works" operating prompt before declaring a host impossible due to auth setup, extension/package discovery, or tool-shape mismatch.
  • Prove runtime claims with live or fixture-backed durable state evidence - see docs/runtime-support.md.

Read the full file on GitHub · 50 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 · 50 lines · 500 tokens per session scan A fbafd7944900

Subscribe to this mod's changes

spacedock AGENTS.md is an instructions file published in the GitHub repository spacedock-dev/spacedock (81 stars, last pushed 4d ago), licensed Apache-2.0. It adds 500 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-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,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,257 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