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.
git clone --depth 1 https://github.com/PIsberg/vibetagsWrote 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/pisberg/vibetags/reactor-spine)<a href="https://agentmods.dev/instructions/pisberg/vibetags/reactor-spine"><img src="https://agentmods.dev/badge/instructions/pisberg/vibetags/reactor-spine/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/pisberg/vibetags/reactor-spine"><img src="https://agentmods.dev/badge/instructions/pisberg/vibetags/reactor-spine.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.00328 | $0.00328 |
| Opus 5.5 | $0.00131 | $0.00131 |
| Sonnet 5.5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
vibetags reactor-spine.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.
What it actually says
Amazon Kiro Steering: reactor-spine
Context & Focus
com.example.gmm.app.App
- Focus: Wiring only: parsing and rendering live in their own modules
- Avoid: Business logic
Security Audit Requirements
com.example.gmm.app.App
When modifying this element, audit for:
- Path Traversal
Locked Status
com.example.gmm.core.IrNode
- Reason: Core IR node shape is depended on by every downstream module
Context & Focus
com.example.gmm.core
- Focus: Immutable IR data model shared across every module of the reactor.
- Avoid: Adding mutable state, framework annotations, or a dependency on any sibling module.
Thread-Safety Guarantee
com.example.gmm.core
- Strategy: IMMUTABLE
- Note: Every type in this package is safe to publish across threads without synchronization.
Security-Critical Code
com.example.gmm.core
- Rule: This code is security-critical. Do not weaken security properties. Every change must be explicitly reviewed for security impact.
- Aspect: Node identity is a security boundary: never build an IrNode from unvalidated external input, and never expose its raw name in a URL or log line.
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.
- 1mo ago First seen · 42 lines · 328 tokens per session scan A c462de55d40e
vibetags reactor-spine.md is an instructions file published in the GitHub repository PIsberg/vibetags (25 stars, last pushed yesterday), licensed MIT. It adds 328 tokens to every session, about $0.0013 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-09-06.
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.
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.
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).