spool AGENTS.md

A project instruction file for Spool, a local task backend used to support development by coding agents. It defines the product direction, terminology, architecture priorities, and limits for the first version.

In plain words
What is it for?
Use it when contributing to Spool or reviewing changes to its service, API, task queues, agent runs, local worktrees, command-line tools, or Pi launcher.
Why use it?
It gives agents a shared set of rules before they change the code. This reduces misunderstandings about the product and prevents work on excluded features such as a web dashboard or external tracker sync.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/seemethere/spool/agents-md
Clone the repo
git clone --depth 1 https://github.com/seemethere/spool

Made for: Codex, OpenCode.

Per session 1,702 This file is loaded in full into every session.
When invoked 1,702 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.01702 $0.01702
Opus 5 $0.00851 $0.00851
Sonnet 5 $0.00340 $0.00340
Haiku 4.5 $0.00170 $0.00170

Measured 2d ago against content hash 336c4b4abdc2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spool 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.

AGENTS.md · 163 lines

How it starts

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

Spool Agent Instructions

Always read first

  • CONTEXT.md — canonical domain language and relationships.
  • ROADMAP.md — current implementation sequence, with Dogfooding Readiness first.
  • Relevant docs/adr/*.md files before changing architecture, workflow, persistence, delivery, or launcher behavior.

Use the terms from CONTEXT.md exactly. Avoid Linear/GitHub/PR-shaped language unless discussing future optional integrations.

Product direction

Spool is a local-first task backend for speeding up agent-driven development. The first priority is Dogfooding Readiness: Spool should become useful enough to build Spool with Spool as quickly as possible.

Keep v1 focused on:

  • Spool Service + Spool API
  • Task Queues
  • Tasks, Task States, requirements, Workpad Notes
  • Agent Runs and Claim Leases
  • Local Worktree Delivery
  • Pi Launcher using pi --mode rpc
  • Minimal Spool Pi Extension
  • CLI-first observability

Do not expand v1 into:

  • A Linear clone or generic project management system
  • A GitHub/PR-dependent workflow
  • A web UI/dashboard
  • Multi-tenant permissions/ACLs
  • Import/sync from external trackers
  • Custom workflows beyond the fixed v1 Task State lifecycle

Implementation stack

Core Spool implementation:

  • Rust
  • axum for HTTP
  • sqlx + SQLite for persistence/migrations
  • clap for CLI
  • tokio for async process/server work
  • serde for API types
  • tracing for logs
  • uuid for internal IDs
  • time for timestamps

Pi integration:

  • TypeScript Spool Pi Extension
  • Communicate with Spool through the HTTP API
  • Do not share in-process code between Rust Spool and the extension

Dogfooding Readiness path

Prioritize these milestones in order:

  1. Rust skeleton, config/init/migrations, health/version.
  2. Queues, Tasks, requirements, Workpad Notes, Audit Events, bootstrap creation, show/status CLI.
  3. Claim/lease/run lifecycle and fake launcher worker loop.
  4. Local Worktree Delivery setup, Pi Launcher RPC, minimal Spool Pi Extension.
  5. Run transcripts/session data, status/run show, manual dogfood merge or first Integrating implementation, deterministic tests.

Read the full file on GitHub · 163 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. 2d ago First seen · 163 lines · 1,702 tokens per session scan A 336c4b4abdc2

Subscribe to this mod's changes

spool AGENTS.md is an instructions file published in the GitHub repository seemethere/spool (5 stars, last pushed 3mo ago), licensed MIT. It adds 1,702 tokens to every session, about $0.0085 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-31.