upki-ca: Instructions file for Codex

AGENTS.md

upki-ca AGENTS.md is an instructions file for Codex, OpenCode from circle-rd/upki-ca. It costs 1,471 tokens per session, scanned A, original, MIT.

A repository instruction document for the upki-ca project. It sets rules for secure, conservative development, including validation, secret handling, code structure, testing, and documentation.

In plain words
What is it for?
It is for guiding implementation, review, testing, and security practices in the upki-ca repository.
Why use it?
It gives coding agents and developers a single set of project-specific constraints, reducing unsafe changes and inconsistent engineering practices.

Instructions file for CodexOpenCode

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

This is circle-rd/upki-ca's own configuration. It tells Codex and OpenCode how to work on upki-ca 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 upki-ca configures →

Reuse

Borrowing it

Nothing to install: this file belongs to circle-rd/upki-ca. 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/circle-rd/upki-ca/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/circle-rd/upki-ca

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 upki-ca AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/circle-rd/upki-ca/agents-md"><img src="https://agentmods.dev/badge/instructions/circle-rd/upki-ca/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,471 This file is loaded in full into every session.
When invoked 1,471 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.01471 $0.01471
Opus 5.5 $0.00588 $0.00588
Sonnet 5.5 $0.00294 $0.00294
Haiku 4.5 $0.00147 $0.00147

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

Security

Grade A, and why

upki-ca 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 17d 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 · 120 lines

How it starts

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

AGENTS.md - upki-ca

This document is the authoritative implementation contract for AI coding agents in this repository.

1) Mission and Scope

Maintain circle-rd/upki-ca conservatively. Correctness, security, auditability, reproducibility, repository conventions, tests, and documentation outrank speed.

2) Offensive Development Doctrine

  • Fail loud and fast. Invalid state must be rejected rather than hidden, coerced, or silently repaired.
  • Validate untrusted data at trust boundaries, then rely on the validated representation downstream.
  • Use the strongest practical type, static-analysis, and runtime-validation guarantees supported by the language, ecosystem, and repository.
  • Do not introduce duplicate code, dead code, commented-out code, or speculative compatibility shims.
  • Security by design and least privilege are mandatory.
  • Secrets must never enter source control, prompts, logs, patches, build artifacts, or test output.
  • Keep modules/components focused. Target <= 500 lines; 1000 lines is a hard ceiling unless a repository-local rule is stricter or an exception is recorded.
  • Deterministic project quality gates must be green before completion.
  • User-visible behavior changes require the repository's expected tests, documentation, changelog, versioning, and migration treatment.
  • Breaking changes must be intentional and explicit; backward-compatibility work is an exception, not an automatic default.
  • Exceptions are documented in the same change with the reason, risk/impact, mitigation, rejected alternative, and removal/revisit condition.

Repository-local rules may add stricter constraints but must not silently weaken this baseline. When a material rule conflict remains, stop and use grill-me before mutation.

3) Language and Framework Adaptation

Active profiles inferred during onboarding: python, typescript, vue.

python

  • Preserve or strengthen type annotations on public interfaces and changed code when the project uses static typing. Do not weaken checker configuration to silence errors.
  • Treat values from HTTP, files, subprocesses, environment variables, deserialization, databases, queues, and tools as untrusted until validated at the appropriate boundary.
  • Catch the narrowest practical exceptions. Do not use broad except Exception/bare except to hide an invalid state unless the boundary intentionally translates failures and preserves diagnostic context.
  • Do not use assert as the sole validation for untrusted runtime input or security-sensitive invariants.
  • Avoid mutable-default, implicit-global-state, and resource-lifetime patterns that obscure ownership or failure behavior.
  • Use the repository's existing formatter, linter, type checker, test runner, packaging, and documentation tools; examples may include Ruff, mypy, Pyright, pytest, or equivalents, but no specific tool is mandated by this profile.

Read the full file on GitHub · 120 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. 17d ago First seen · 120 lines · 1,471 tokens per session scan A e719b60cba86

Subscribe to this mod's changes

upki-ca AGENTS.md is an instructions file published in the GitHub repository circle-rd/upki-ca (2 stars, last pushed 13d ago), licensed MIT. It adds 1,471 tokens to every session, about $0.0059 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-02.

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

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

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