Borrowing it
Nothing to install: this file belongs to SpineEventEngine/config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SpineEventEngine/config/master/AGENTS.mdgit clone --depth 1 https://github.com/SpineEventEngine/configWrote 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.
[](https://agentmods.dev/instructions/spineeventengine/config/agents-md)<a href="https://agentmods.dev/instructions/spineeventengine/config/agents-md"><img src="https://agentmods.dev/badge/instructions/spineeventengine/config/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.
<a href="https://agentmods.dev/instructions/spineeventengine/config/agents-md"><img src="https://agentmods.dev/badge/instructions/spineeventengine/config/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.01708 | $0.01708 |
| Opus 5.5 | $0.00683 | $0.00683 |
| Sonnet 5.5 | $0.00342 | $0.00342 |
| Haiku 4.5 | $0.00171 | $0.00171 |
Grade A, and why
config 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 8d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
👋 Welcome, Agents!
Orientation
If .agents/project.md exists in this repository, read it first — it describes
the language, architecture, and role of this specific repo within the Spine SDK
organisation. It is a symlink to docs/project.md; to create one, copy
.agents/guidelines/project.template.md to docs/project.md and fill it in. If it
links to a shared requirements file (e.g. jvm-project.md), read that too.
- Start every session by reading
.agents/guidelines/quick-reference-card.md(if present). - For specific tasks (code review, PR prep, dependency updates, docs, etc.),
prefer the matching skill from
.agents/skills/. - Full standards reference:
.agents/guidelines/_TOC.md(if present) — consult when a skill doesn't cover the needed context.
Shared skills, scripts, and guidelines come from the .agents/shared submodule (the
[agents][agents-repo] repository) exposed via symlinks.
./config/pull initializes and floats them automatically. But a fresh git worktree
(and some shallow clones / cloud checkouts) start with NO submodules checked out, so
those symlinks dangle and no skills are found. Bootstrap such a tree with
./init-submodules — a root script that materializes the missing
config-managed submodules at the tip of their branch (master for config, the
tracked branch for the rest): config itself, plus every submodule that declares
a tracked branch in .gitmodules (.agents/shared, and any shared submodule
added later) — the same rule ./config/pull uses to decide what it floats. It
deliberately does not stop at the commit the superproject pins for such a
submodule: nothing keeps that pin current — ignore = all hides the submodule from
git status, and ./config/pull floats the on-disk copy without committing the
moved gitlink — so materializing the pin as-is means months-old hook scripts,
skills, and guidelines. If the float fails — a branch the remote does not have,
say — a warning is printed and the submodule is left wherever the steps that
did succeed put it, at worst the pin, so a session still starts with a usable
tree; it is not retried on a later run, which is why that warning points at
./config/pull. With no network at all the clone itself fails and the
submodule is left uninitialized, as it was before. Submodules the consumer owns
(a Hugo theme, a vendored library, doc-example submodules, …) declare no tracked
branch and are left untouched, so the automatic SessionStart run never tries
to clone — or fail on credentials for — a submodule this project does not
manage. A submodule that is already checked out is left exactly as it is, which
keeps repeated runs cheap and offline-safe and never rewinds a tree someone
parked on a particular commit; run ./config/pull to float those. It depends on
no pre-existing config submodule, so it works before ./config/pull (which
lives inside the config submodule) can. Claude Code runs it automatically via
a SessionStart hook; other agents and humans run it by hand.
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.
- 8d ago Changed · +12 lines · +235 tokens per session 7bcc9e89e93a
- 1mo ago First seen · 136 lines · 1,473 tokens per session scan A 85b519ef65db
config AGENTS.md is an instructions file published in the GitHub repository SpineEventEngine/config (2 stars, last pushed 4d ago), licensed Apache-2.0. It adds 1,708 tokens to every session, about $0.0068 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.
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).
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.
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).
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 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.