resume-kit AGENTS.md

A set of instructions for coordinating work on the resume-kit code project. It explains how the main coordinator assigns tasks, manages branches, and controls Git changes.

In plain words
What is it for?
Use it when splitting development work among agents, assigning file ownership, creating feature branches, and running project checks.
Why use it?
It prevents multiple coding agents from editing the same files or running conflicting checks. It also clarifies who verifies, commits, merges, and pushes changes.

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/dcassil/resume-kit/agents-md
Clone the repo
git clone --depth 1 https://github.com/dcassil/resume-kit

Made for: Codex, OpenCode.

Per session 454 This file is loaded in full into every session.
When invoked 454 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.00454 $0.00454
Opus 5 $0.00227 $0.00227
Sonnet 5 $0.00091 $0.00091
Haiku 4.5 $0.00045 $0.00045

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

Security

Grade A, and why

resume-kit 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 yesterday.

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 · 36 lines

What it actually says

AGENTS.md — Orchestration conventions for resume-kit

This repo is built via teamwork orchestration. The main Claude session is the orchestrator; it decomposes Metis initiatives into tasks, dispatches implementing agents (codex / claude subagents), and owns all git.

Branches

  • main — integration + release branch. The orchestrator may commit and push main directly for this greenfield project (there is no separate develop yet, and main is not a protected legacy branch here). Feature work happens on feat/<slug> branches or in ../.worktrees/<slug> and is merged with --no-ff.
  • Worker/implementing agents never run git. They only write files.

Git ownership

  • Only the orchestrator stages, verifies, commits, merges, and pushes.
  • Verification (ruff, mypy, pytest) is run by the orchestrator once per wave, never inside a racing worker agent.

Work claims

  • .agents/work-log.md holds one exclusive file claim per in-flight agent. Never let two in-flight agents claim the same file. Disjoint files → parallel; shared files → serial.

Task decomposition

  • Initiatives and tasks live in Metis (.metis/). Each task carries a Recommended Agent execution profile. Decomposition of an initiative is done by a codex agent, reviewed by the orchestrator, then recorded as Metis task documents.

Tech stack

  • Python 3.12+, uv workspace, ruff (lint/format), mypy (types), pytest (tests).
  • Pydantic v2 for models. LiteLLM behind a provider Protocol. MarkItDown for extraction.

Upstream donor

  • Resume-Matcher is cloned to ./upstream/ (gitignored, never distributed) at a pinned commit for reference/extraction only. Every ported subsystem records its upstream SHA in references/reuse-inventory.md and attribution in references/attribution.md.
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. yesterday First seen · 36 lines · 454 tokens per session scan A c485872a8dbd

Subscribe to this mod's changes

resume-kit AGENTS.md is an instructions file published in the GitHub repository dcassil/resume-kit (0 stars, last pushed 21d ago), licensed Apache-2.0. It adds 454 tokens to every session, about $0.0023 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-31.