aptl: Instructions file for Codex

AGENTS.md

aptl AGENTS.md is an instructions file for Codex, OpenCode from Brad-Edwards/aptl. It costs 1,395 tokens per session, scanned A, original, MIT.

Repository-specific instructions for APTL, the Advanced Purple Team Lab, covering its requirements workflow, testing, code checks, and agent setup.

In plain words
What is it for?
They are for reading the repository's Ground Control configuration, running pytest and pre-commit checks, following planning rules, and installing the project's shared agent skills.
Why use it?
They give an agent the project context and completion rules needed to work consistently in that repository.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

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

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is bin/install-raes-inventory-skill.sh --raes-repo ../raes.

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/brad-edwards/aptl/agents-md"><img src="https://agentmods.dev/badge/instructions/brad-edwards/aptl/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,395 This file is loaded in full into every session.
When invoked 1,395 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.01395 $0.01395
Opus 5.5 $0.00558 $0.00558
Sonnet 5.5 $0.00279 $0.00279
Haiku 4.5 $0.00139 $0.00139

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

Security

Grade A, and why

aptl 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 · 134 lines

How it starts

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

Agent Instructions

This repository (APTL — Advanced Purple Team Lab) uses Ground Control for requirements management and workflow automation.

Ground Control Context

This repo's Ground Control project id, workflow commands, SonarCloud settings, and plan rules live in .ground-control.yaml at repo root (with larger rule files under .gc/). Agents read it via the gc_get_repo_ground_control_context MCP tool, which returns the full workflow config in a single call.

Key facts encoded there today:

  • Ground Control project: aptl
  • GitHub repo: Brad-Edwards/aptl
  • Local test command: bash tools/run-targeted-tests.sh (changed test files only, or pass explicit test paths)
  • Local hygiene command: pre-commit run after staging the intended changes
  • Full suites, coverage, whole-tree lint, and whole-tree prose checks: CI/CD only
  • SonarCloud project key: Brad-Edwards_aptl (org: brad-edwards)
  • Plan rules: .gc/plan-rules.md

Skill Installation

The canonical agent-neutral implement and review-tests skills are maintained in the Ground Control repo at skills/implement/SKILL.md and skills/review-tests/SKILL.md. They are installed at the user level — not committed per-repo — by running, from a Ground Control checkout:

bin/install-skills.sh

That script symlinks the canonical skills into:

  • ~/.claude/skills/ (Claude Code)
  • ~/.codex/prompts/ (Codex)

Both Claude and Codex therefore read the same source-of-truth SKILL.md. Re-run the script after pulling Ground Control to refresh. Use --copy on hosts without symlink support and --no-codex if Codex isn't installed locally.

This repo intentionally does not ship .claude/skills/implement/ or .claude/skills/review-tests/ — those were per-repo duplicates superseded by Ground Control PR #792. Other repo-local skills under .claude/skills/ (e.g. ship, stage, gh-workflow-monitor, wave-issue-coverage) remain in place because they are aptl-specific or not yet promoted to the agent-neutral set.

Read the full file on GitHub · 134 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 · +4 lines · +78 tokens per session c277a054bf15
  2. 1mo ago Changed · +8 tokens per session e5fc36f91a16
  3. 2mo ago First seen · 130 lines · 1,309 tokens per session scan A f5874eea732b

Subscribe to this mod's changes

aptl AGENTS.md is an instructions file published in the GitHub repository Brad-Edwards/aptl (25 stars, last pushed 24d ago), licensed MIT. It adds 1,395 tokens to every session, about $0.0056 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,461 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,261 tokens