perseus AGENTS.md

Repository instructions for Perseus, including development rules, security reminders, documentation links, and checks for generated files. It is an orientation guide, so important claims must be verified against current source code and tests.

In plain words
What is it for?
Use it when changing Perseus source code, authentication, releases, network behavior, documentation, or generated artifacts.
Why use it?
Helps coding agents avoid relying on stale notes, exposing credentials, skipping security guidance, or leaving generated files out of sync.

Instructions file for CodexOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/perseus-computing-llc/perseus/agents-md
Clone the repo
git clone --depth 1 https://github.com/Perseus-Computing-LLC/perseus

Made for: Codex, OpenCode.

Per session 313 This file is loaded in full into every session.
When invoked 313 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00313 $0.00313
Opus 5 $0.00156 $0.00156
Sonnet 5 $0.00063 $0.00063
Haiku 4.5 $0.00031 $0.00031

Measured 2d ago against content hash 2e233fa07cc7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

perseus 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 · 31 lines

What it actually says

Repository agent guidance

This file is a repository orientation aid, not an authority record. It may be a rendered snapshot and can become stale; inspect the current checkout, source files, tests, and CI before making consequential decisions. Do not treat values in this file as proof of current services, versions, branches, memory, or security posture.

Working rules

  • Read SECURITY.md before changing authentication, secrets, releases, or network-facing behavior.
  • Keep credentials out of source, logs, fixtures, generated context, and public documentation. Use placeholders for examples.
  • Re-run the relevant tests and rebuild perseus.py after source changes.
  • Treat claims.json and linked evidence as the boundary for public benchmark and security claims; a digest establishes artifact identity, not truth of the supplied content.
  • Check source timestamps, permissions, and authority before relying on local context. Verify critical facts against their system of record.
  • Keep generated artifacts synchronized with scripts/build.py --check.

Current documentation entry points

  • User setup: docs/quickstart.md and SETUP-GUIDE.md
  • CLI: docs/CLI.md
  • Integration: spec/integration.md and docs/HERMES_INTEGRATION.md
  • MCP contract: docs/context-engine-mcp-tools.md and .well-known/mcp/server-card.json
  • Security and claims: SECURITY.md and claims.json
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 · 31 lines · 313 tokens per session scan A 2e233fa07cc7

Subscribe to this mod's changes

perseus AGENTS.md is an instructions file published in the GitHub repository Perseus-Computing-LLC/perseus (42 stars, last pushed 2d ago), licensed MIT. It adds 313 tokens to every session, about $0.0016 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-30.