guardian-agent: Instructions file for Codex

AGENTS.md

guardian-agent AGENTS.md is an instructions file for Codex, OpenCode from Threat-Vector-Security/guardian-agent. It costs 1,785 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for GuardianAgent, an application that coordinates delegated coding work. They define rules for safe implementation, branching, project organization, testing, and runtime handoff.

In plain words
What is it for?
Use them to guide changes to GuardianAgent, follow its build and test process, preserve the current branch unless asked otherwise, and hand work between development and runtime environments.
Why use it?
They prevent the coordinator from secretly creating project-specific results, using unsafe branch changes, or declaring work successful without real evidence.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

Nothing to install: this file belongs to Threat-Vector-Security/guardian-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/Threat-Vector-Security/guardian-agent/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/Threat-Vector-Security/guardian-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 guardian-agent AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/threat-vector-security/guardian-agent/agents-md"><img src="https://agentmods.dev/badge/instructions/threat-vector-security/guardian-agent/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,785 This file is loaded in full into every session.
When invoked 1,785 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.01785 $0.01785
Opus 5.5 $0.00714 $0.00714
Sonnet 5.5 $0.00357 $0.00357
Haiku 4.5 $0.00178 $0.00178

Measured 1mo ago against content hash 9aea3ea235f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

AGENTS.md · 84 lines

How it starts

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

Repository Guidelines

Current product and module ownership

Guardian Agent 2 is the local security and ContextCypher architecture workspace. The package version in package.json is the release source of truth. The default entry point is src/security-main.ts, compiled to dist/security-main.js; it does not start the retained assistant runtime in src/index.ts.

  • src/security-workspace/: operation schemas and authorization (operations.ts), shared business rules (service.ts), loopback HTTP/session transport (server.ts), SQLite persistence (store.ts), CLI client/MCP transport, collectors, AWS, Entra and bounded AI.
  • web/security/: Guardian shell and security pages. web/contextcypher/: the standalone-capable diagram, analysis and GRC workbench. web/shared/: shared browser file dialogs.
  • scripts/: verification and packaging harnesses; docs/: current architecture, guides and explicitly marked historical material.
  • src/runtime/, src/guardian/, src/tools/, src/channels/, src/index.ts and web/public/ retain legacy implementation and selected shared components. Their existence does not mean their assistant features ship in the default security application.

Read SECURITY.md, the conversion architecture, the operator guide, and the operation API reference before changing current trust boundaries or capabilities.

No hardcoded deliverables or test-passing fallbacks (CRITICAL)

Never add canned domain output, fabricated findings, sample applications, scripted answers, or fallback implementations to make a requested workflow appear successful. Model generation must come from the configured provider; collection must report observed evidence and unavailable coverage honestly. Explicitly selected, bundled ContextCypher examples are legitimate product content, not fallback evidence or generated results.

For retained orchestration code, Guardian may route, retry, verify generic evidence and report failure; the delegated worker owns the actual implementation in the target workspace. If a test passes because Guardian recognizes a prompt, filename, selector set or expected answer and fills it in, remove the workaround and fix the owning contract.

Read the full file on GitHub · 84 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. 1mo ago Changed · +9 lines · -1,149 tokens per session 9aea3ea235f7
  2. 1mo ago First seen · 75 lines · 2,934 tokens per session scan A 128b0a30100c

Subscribe to this mod's changes

guardian-agent AGENTS.md is an instructions file published in the GitHub repository Threat-Vector-Security/guardian-agent (13 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,785 tokens to every session, about $0.0071 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-30.

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,715 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,786 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

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

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.

denoland/deno · 3,077 tokens