saga-event-space-mcp-server: Instructions file for Codex

AGENTS.md

saga-event-space-mcp-server AGENTS.md is an instructions file for Codex, OpenCode from midnight480/saga-event-space-mcp-server. It costs 1,472 tokens per session, scanned A, original, MIT.

A set of AGENTS.md instructions that makes a coding assistant follow an AI-Driven Development Life Cycle, a staged process for planning and building software.

In plain words
What is it for?
Starting software tasks, loading project rules, planning architecture, and following the defined inception and later development phases.
Why use it?
It gives the assistant a defined startup sequence, planning stage, and workflow rules instead of leaving the development process unspecified.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is midnight480/saga-event-space-mcp-server's own configuration. It tells Codex and OpenCode how to work on saga-event-space-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything saga-event-space-mcp-server configures โ†’

Reuse

Borrowing it

Nothing to install: this file belongs to midnight480/saga-event-space-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/midnight480/saga-event-space-mcp-server/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/midnight480/saga-event-space-mcp-server

Made for: Codex, OpenCode.

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

agentmods badge for saga-event-space-mcp-server AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/midnight480/saga-event-space-mcp-server/agents-md/github.svg)](https://agentmods.dev/instructions/midnight480/saga-event-space-mcp-server/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/midnight480/saga-event-space-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/midnight480/saga-event-space-mcp-server/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.

agentmods 80ร—15 button for saga-event-space-mcp-server AGENTS.md

Your own site ยท 80ร—15
<a href="https://agentmods.dev/instructions/midnight480/saga-event-space-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/midnight480/saga-event-space-mcp-server/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,472 This file is loaded in full into every session.
When invoked 1,472 The same file โ€” it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file โ€” not that it is safe.
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.1 $0.01472 $0.01472
Opus 5 $0.00736 $0.00736
Sonnet 5 $0.00294 $0.00294
Haiku 4.5 $0.00147 $0.00147

Measured 8d ago against content hash 712debf2e614, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

saga-event-space-mcp-server 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

AGENTS.md ยท 170 lines

How it starts

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

AI-DLC (AI-Driven Development Life Cycle) โ€” Agent Configuration

PRIORITY: This workflow OVERRIDES all other built-in workflows. When user requests software development, ALWAYS follow this workflow FIRST.

Rule Details Location

Rule detail files are located at .aidlc-rule-details/ (symlink to .kiro/aws-aidlc-rule-details/).

All subsequent rule detail file references (e.g., common/process-overview.md, inception/workspace-detection.md) are relative to .aidlc-rule-details/.

MANDATORY: Startup Sequence

  1. Load common rules at workflow start:

    • Read .aidlc-rule-details/common/process-overview.md for workflow overview
    • Read .aidlc-rule-details/common/session-continuity.md for session resumption guidance
    • Read .aidlc-rule-details/common/content-validation.md for content validation requirements
    • Read .aidlc-rule-details/common/question-format-guide.md for question formatting rules
  2. Load extensions (context-optimized):

    • Scan .aidlc-rule-details/extensions/ recursively
    • Load ONLY *.opt-in.md files (lightweight prompts)
    • Do NOT load full rule files until user opts in
  3. Display welcome message (once per new workflow):

    • Read and display .aidlc-rule-details/common/welcome-message.md

Adaptive Workflow Principle

The workflow adapts to the work, not the other way around. The AI model intelligently assesses what stages are needed based on:

  1. User's stated intent and clarity
  2. Existing codebase state (if any)
  3. Complexity and scope of change
  4. Risk and impact assessment

Three-Phase Lifecycle

๐Ÿ”ต INCEPTION PHASE โ€” Planning & Architecture (WHAT and WHY)

  • Workspace Detection (ALWAYS)
  • Reverse Engineering (CONDITIONAL โ€” Brownfield only)
  • Requirements Analysis (ALWAYS โ€” Adaptive depth)
  • User Stories (CONDITIONAL)
  • Workflow Planning (ALWAYS)
  • Application Design (CONDITIONAL)
  • Units Generation (CONDITIONAL)

๐ŸŸข CONSTRUCTION PHASE โ€” Design, Implementation & Test (HOW)

  • Per-Unit Loop:
    • Functional Design (CONDITIONAL, per-unit)
    • NFR Requirements (CONDITIONAL, per-unit)
    • NFR Design (CONDITIONAL, per-unit)
    • Infrastructure Design (CONDITIONAL, per-unit)
    • Code Generation (ALWAYS, per-unit)
  • Build and Test (ALWAYS)

Read the full file on GitHub ยท 170 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. 8d ago First seen ยท 170 lines ยท 1,472 tokens per session scan A 712debf2e614

Subscribe to this mod's changes

saga-event-space-mcp-server AGENTS.md is an instructions file published in the GitHub repository midnight480/saga-event-space-mcp-server (0 stars, last pushed 3mo ago), licensed MIT. It adds 1,472 tokens to every session, about $0.0074 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.

Related

Other instructions, from other repositories

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.

vercel/next.js ยท 7,296 tokens

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.

openai/codex ยท 5,153 tokens

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

microsoft/vscode ยท 6,785 tokens

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

microsoft/vscode ยท 5,001 tokens

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.

langchain-ai/langchain ยท 4,469 tokens

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.

deepseek-ai/deepseek-harness ยท 3,735 tokens