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/cloudmanic/spice-edit/agents-mdgit clone --depth 1 https://github.com/cloudmanic/spice-editWhat 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.00646 | $0.00646 |
| Opus 5 | $0.00323 | $0.00323 |
| Sonnet 5 | $0.00129 | $0.00129 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
spice-edit 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
SpiceEdit is a Go terminal editor module at github.com/cloudmanic/spice-edit; the CLI entry point is main.go and the binary is spiceedit. Core packages live under internal/: app owns the event loop and rendering, editor owns buffers/tabs/editing behavior, filetree manages the sidebar tree, and supporting packages cover clipboard, formatting, icons, config, theme, finder, and versioning. Tests sit beside source files as *_test.go. Website assets and docs live in website/ as a Hugo + Tailwind site. Release packaging includes Formula/spice-edit.rb, install.sh, and samples under samples/.
Build, Test, and Development Commands
make run: run the editor in the current directory withgo run ..make build: compile./bin/spiceedit.make build-linux: cross-compile a staticlinux/amd64binary.make test: rungo test -race ./...; use before PRs.make test-short: quickgo test -short ./...loop while iterating.make coverage: writecoverage.outandcoverage.html.make tidy: syncgo.modandgo.sum.make site-install,make site-dev,make site-build: manage website deps, local Hugo, and production builds.
Coding Style & Naming Conventions
Use gofmt/go test defaults and idiomatic Go names: exported identifiers in CamelCase, unexported in camelCase, package names short and lowercase. New Go source files should follow the existing header block style. Keep short doc comments above functions, including private helpers, explaining intent. Avoid adding Ctrl+ shortcuts; editor actions must stay reachable from the main ≡ menu because SSH/tmux workflows may swallow shortcuts or right-click events.
Testing Guidelines
Every non-trivial source file should have a same-package test file, for example internal/editor/buffer.go and internal/editor/buffer_test.go. Add regression tests for bug fixes and cover happy paths and obvious failures. Use t.TempDir() for filesystem state. For drawing tests, use tcell.NewSimulationScreen("UTF-8") and assert screen contents.
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 · 33 lines · 646 tokens per session scan A c483cd41181f
spice-edit AGENTS.md is an instructions file published in the GitHub repository cloudmanic/spice-edit (82 stars, last pushed 1mo ago), licensed MIT. It adds 646 tokens to every session, about $0.0032 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
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.