secretsminter: Instructions file for Codex

AGENTS.md

secretsminter AGENTS.md is an instructions file for Codex, OpenCode from scorellis/secretsminter. It costs 1,169 tokens per session, scanned A, original, Apache-2.0.

Project instructions for secretsminter, a service that creates, places, and rotates cloud credentials without showing secret values to the requesting agent. They explain its security rules, code layout, testing, and logging conventions.

In plain words
What is it for?
Onboarding an agent or developer before changing, testing, or operating the secretsminter repository.
Why use it?
They help contributors preserve the rule that secrets must not appear in tool responses or logs, and that credentials may only be placed in approved destinations.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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 secretsminter AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/scorellis/secretsminter/agents-md"><img src="https://agentmods.dev/badge/instructions/scorellis/secretsminter/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,169 This file is loaded in full into every session.
When invoked 1,169 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.01169 $0.01169
Opus 5.5 $0.00468 $0.00468
Sonnet 5.5 $0.00234 $0.00234
Haiku 4.5 $0.00117 $0.00117

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

Security

Grade A, and why

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

AGENTS.md · 87 lines

How it starts

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

AGENTS.md — onboarding for anyone (human or AI) working in this repo

This is the tool-agnostic onboarding file. Read it before touching code, running the server, or consuming the repo. It captures the operational conventions that aren't obvious from the code alone.

What secretsminter is

A value-blind secrets-minter exposed to AI agents over MCP: it mints, places, and rotates cloud credentials without ever returning a secret value to the calling agent. Read README.md for the pitch and SECURITY.md for the threat model. The two invariants that govern everything:

  1. Value-blind — no secret value crosses the tool boundary, an error string, or a log line.
  2. Destination allow-list — a placement is refused unless it matches the signed manifest. This, not value-blindness, is the real trust root.

If a change you make could violate either, stop and re-read CONTRIBUTING.md.

Layout

  • packages/core (@secretsminter/core) — the key-holding internal tier: all security invariants, the broker pipeline, sinks. Everything network-free here is unit-tested.
  • packages/mcp (@secretsminter/mcp) — the agent-facing MCP server; holds no master keys.
  • packages/providers — Cloudflare/GitHub/Supabase plugins (all have real network paths; live-run status varies per story — Cloudflare live-verified, GitHub/Supabase unit-tested against fakes).
  • docs/adrs, docs/spikes, docs/stories — decisions, capability findings, and honest per-feature status.

Build & test

npm install
npm run build          # tsc --build, strict
npm test               # vitest
npm run test:coverage  # vitest + the coverage gate (90/85/88/90 on real logic)

The coverage gate runs locally (npm run test:coverage), not in CI — see the isolation principle.

Isolation — secretsminter is self-contained, stores nothing, manages other repos

secretsminter deploys as pure, isolated code someone stands up to run their own broker. Non-negotiable:

Read the full file on GitHub · 87 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 First seen · 87 lines · 1,169 tokens per session scan A 7b9d4f39848f

Subscribe to this mod's changes

secretsminter AGENTS.md is an instructions file published in the GitHub repository scorellis/secretsminter (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 1,169 tokens to every session, about $0.0047 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-31.

Related

Other instructions, from other repositories