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.
npx agentmods add instructions/spacedock-dev/spacedock/agents-mdgit clone --depth 1 https://github.com/spacedock-dev/spacedockWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00500 | $0.00500 |
| Opus 5 | $0.00250 | $0.00250 |
| Sonnet 5 | $0.00100 | $0.00100 |
| Haiku 4.5 | $0.00050 | $0.00050 |
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 2d 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.
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.mdfirst. - 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.
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.
- 2d ago First seen · 50 lines · 500 tokens per session scan A fbafd7944900
spacedock AGENTS.md is an instructions file published in the GitHub repository spacedock-dev/spacedock (75 stars, last pushed 3d ago), licensed Apache-2.0. It adds 500 tokens to every session, about $0.0025 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.
Other instructions, from other repositories
Citadel AGENTS.md
Instructions for SethGammon/Citadel, covering codex harness, what this is, key conventions, testing and review guidelines.
Citadel CLAUDE.md
Instructions for SethGammon/Citadel, covering claude harness, what this is, key conventions, testing and campaign design principles.
kanban-md AGENTS.md
Instructions for antopolskiy/kanban-md, covering guidelines, releasing, ci verification (required), release notes and new: feature name (by @contributor).
AI-Prompt-Guide-MCP AGENTS.md
Instructions for Blakeem/AI-Prompt-Guide-MCP, covering ai-prompt-guide mcp server - developer guide, project overview, configuration, zero-config default and optional override.
AgentWorkspaceOS AGENTS.md
AGENTS.md instructions for zhangj012595-cloud/AgentWorkspaceOS, covering agent instructions, before making changes, public repository boundary, verification and shared coordination.
AI-Prompt-Guide-MCP CLAUDE.md
Instructions for Blakeem/AI-Prompt-Guide-MCP, a project described as: Deprecated. MCP server and Claude Code plugin with task driven agent orchestration workflows, guides, markdown knowledge graphs, with intelligent context injection.