ssi-agent: Instructions file for Codex

AGENTS.md

ssi-agent AGENTS.md is an instructions file for Codex, OpenCode from impierce/ssi-agent. It costs 1,306 tokens per session, scanned A, original, Apache-2.0.

A project-specific instruction file for the ssi-agent codebase. It records the application's architecture, design rules, coding standards, and API naming conventions.

In plain words
What is it for?
It helps with architectural decisions, domain-driven design, event sourcing, CQRS, OpenAPI operation names, and repository conventions.
Why use it?
It gives a coding agent the context needed to make changes that fit the existing system instead of applying generic patterns.

Instructions file for CodexOpenCode

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

This is impierce/ssi-agent's own configuration. It tells Codex and OpenCode how to work on ssi-agent 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 ssi-agent configures →

Reuse

Borrowing it

Nothing to install: this file belongs to impierce/ssi-agent. 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/impierce/ssi-agent/beta/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/impierce/ssi-agent

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 ssi-agent AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/impierce/ssi-agent/agents-md/github.svg)](https://agentmods.dev/instructions/impierce/ssi-agent/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/impierce/ssi-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/impierce/ssi-agent/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 ssi-agent AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/impierce/ssi-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/impierce/ssi-agent/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,306 This file is loaded in full into every session.
When invoked 1,306 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.01306 $0.01306
Opus 5.5 $0.00522 $0.00522
Sonnet 5.5 $0.00261 $0.00261
Haiku 4.5 $0.00131 $0.00131

Measured 2d ago against content hash 7b01f1013984, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ssi-agent 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 · 90 lines

How it starts

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

AGENTS.md

Application design

  • DDD: The application is designed around the concept of domain-driven design, where the core business logic is organized into domains and subdomains, with a clear separation of concerns.
  • CQRS: The application uses the command-query responsibility segregation pattern, where commands are used to modify state and queries are used to read state. Events are treated as immutable after the are created. Projections are used to derive queryable read models from the event stream.
  • Event sourcing: The application uses event sourcing to capture all changes to the state as a sequence of events. This allows for a complete audit trail and the ability to reconstruct past states by replaying events.
  • Hexagonal architecture: The application tries to abstract how data comes in to the application and how it is stored.

Architecture

Architecture Decision Records (ADRs) can be found in the docs/adr directory.

Standards and conventions

  • The application follows the Twelve-Factor App methodology for building modern, scalable applications.
  • The application uses semantic versioning for releases and follows a branching strategy to manage different stages of development (e.g. main for stable releases, next for upcoming major versions, beta for pre-releases, and alpha for experimental features).
  • The application uses conventional commits for commit messages to enable automated semantic releases.
  • For errors on the HTTP API, the application follows the RFC 9457 Problem Details for HTTP APIs specification for error responses.
  • Events follow the CloudEvents specification (v1.0.2) for event structure and metadata (this is not fully done as of today).

OpenAPI operation_id

operation_id in #[utoipa::path(...)] annotations becomes the function name generated by downstream TypeScript client generators. Keep it:

Read the full file on GitHub · 90 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 · 90 lines · 1,306 tokens per session scan A 7b01f1013984

Subscribe to this mod's changes

ssi-agent AGENTS.md is an instructions file published in the GitHub repository impierce/ssi-agent (21 stars, last pushed 3d ago), licensed Apache-2.0. It adds 1,306 tokens to every session, about $0.0052 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-10-14.

Related

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

microsoft/vscode · 9,649 tokens

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,257 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 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 · 4,159 tokens

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

microsoft/vscode · 2,731 tokens