issue-flow: Instructions file for Codex

AGENTS.md

issue-flow AGENTS.md is an instructions file for Codex, OpenCode from jepegit/issue-flow. It costs 2,703 tokens per session, scanned A, original, MIT.

Repository instructions for issue-flow, a Python command-line tool that adds an issue-tracking workflow and agent guidance to other projects. They describe this repository’s purpose, layout, tools, and conventions.

In plain words
What is it for?
Use them when working on issue-flow code, templates, dependencies, tests, or its command-line entry point.
Why use it?
They prevent agents from confusing the tool’s own source code with a project generated by the tool and from using the wrong development commands.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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 issue-flow AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/jepegit/issue-flow/agents-md"><img src="https://agentmods.dev/badge/instructions/jepegit/issue-flow/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,703 This file is loaded in full into every session.
When invoked 2,703 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.02703 $0.02703
Opus 5.5 $0.01081 $0.01081
Sonnet 5.5 $0.00541 $0.00541
Haiku 4.5 $0.00270 $0.00270

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

Security

Grade A, and why

issue-flow 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 8d 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 · 192 lines

How it starts

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

AGENTS.md

Guidance for AI agents working in the issue-flow repository.

What this project is

issue-flow is a small Python CLI that scaffolds a lightweight, agent-friendly issue-tracking workflow into other projects. Running issue-flow init writes a .issueflows/ tracking tree plus editor skills, rules, and command files where the selected editor still needs them, so AI agents can pick up GitHub issues, plan work, and land PRs in a consistent way.

This repo is the tool itself — not a project that has been scaffolded by it.

  • Package name: issue-flow (module issue_flow)
  • Entry point: issue-flow = "issue_flow.cli:main"
  • Requires Python 3.12+ (development pin: 3.13 in .python-version)
  • Source of truth for scaffolded files: Jinja2 templates under src/issue_flow/templates/

Environment & tooling

This project uses a uv-managed virtual environment (.venv). Use uv exclusively for dependency management and running code — never pip, pip-tools, or poetry.

uv sync                 # install/refresh all deps from the lock file
uv add <package>        # add or upgrade a dependency
uv remove <package>     # remove a dependency
uv run <script.py>      # run a script with the right environment

❌ python run_script.py → ✅ uv run run_script.py

Common commands

uv run pytest                      # run the test suite
uv run ruff check src/ tests/      # lint
uv version --bump <part>           # bump version (used by /iflow-close)

Project layout

src/issue_flow/
  cli.py            # Typer CLI: init / update / graphify
  init.py           # scaffolding logic (writes .issueflows/ + .cursor/)
  config.py         # env-driven config (ISSUEFLOW_* vars, .env)
  dependencies.py   # external-CLI checks (git, gh)
  templating.py     # Jinja2 rendering helpers
  graphify.py       # optional graphify integration
  migrate.py        # one-shot migrations `update` applies to older scaffolds
  templates/        # Jinja2 templates for all scaffolded output
    commands/         # thin command wrapper (editors with a commands dir)
    skills/           # Agent Skills: SKILL.md router + mode files per command
    rules/            # always-on rule body (AGENTS.md block) + pointers
tests/              # pytest suite

Read the full file on GitHub · 192 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. 8d ago Changed · -287 lines · -5,412 tokens per session 8cb3bbb607eb
  2. 1mo ago Changed · +1 lines · +128 tokens per session 9767d4c1d58b
  3. 1mo ago Changed · +8 lines · +189 tokens per session 66a428b7da84
  4. 1mo ago Changed · +77 tokens per session 676e00b153dc
  5. 1mo ago Changed b3e62fae553e
  6. 1mo ago Changed · +6 lines · +193 tokens per session f9813904be66
  7. 1mo ago Changed · +6 lines · +174 tokens per session 9c473864b050
  8. 1mo ago Changed · +6 lines · +140 tokens per session 788c0a622233
  9. 1mo ago Changed · +25 lines · +281 tokens per session 7ccabdd518ad
  10. 2mo ago First seen · 427 lines · 6,933 tokens per session scan A 7b2b3ddd8f03

Subscribe to this mod's changes

issue-flow AGENTS.md is an instructions file published in the GitHub repository jepegit/issue-flow (4 stars, last pushed 8d ago), licensed MIT. It adds 2,703 tokens to every session, about $0.0108 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

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,750 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