devaiflow AGENTS.md

Agent instructions for DevAIFlow, a project that provides coding and workflow tools. They define general rules, Git practices, issue-tracker usage, and where the project's skill documentation belongs.

In plain words
What is it for?
Use them when contributing to DevAIFlow, handling JIRA work through its required command-line tool, updating CLI skill documentation, and following the project's branch workflow.
Why use it?
They prevent contributors from using the wrong issue-tracker interface or editing local cached files that will later be overwritten.

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

Made for: Codex, OpenCode.

Per session 19,894 This file is loaded in full into every session.
When invoked 19,894 The same file — it is already loaded in full.
Security scan D 3 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.19894 $0.19894
Opus 5 $0.09947 $0.09947
Sonnet 5 $0.03979 $0.03979
Haiku 4.5 $0.01989 $0.01989

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

Security

Grade D, and why

devaiflow AGENTS.md scanned grade D with 3 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo apt install gh

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

find . -type d -name __pycache__ -exec rm -rf {} + 2>/dev/null || true

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- ✓ Initial prompt uses daf jira view instead of curl
AGENTS.md · 1,843 lines

How it starts

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

Agent Instructions for DevAIFlow

General Instructions

IMPORTANT: The following general instructions apply to the DevAIFlow project and MUST be followed when contributing to this codebase.

For JIRA operations: This project uses the daf tool for issue tracker integration. Always use daf jira commands (documented in the daf-workflow skill), NOT direct API calls.

Skills Documentation: The skills (CLI command documentation) are located in the devflow/cli_skills/ directory in the repository.

For comprehensive skills management documentation (discovery order, precedence rules, best practices), see docs/guides/skills-management.md.

⚠️ CRITICAL - Common Mistake to Avoid:

  • CORRECT: Update files in devflow/cli_skills/daf-*/SKILL.md (repository files that get committed)
  • WRONG: Do NOT update files in ~/.claude/skills/daf-*/SKILL.md (user's local cache, will be overwritten)

When updating command functionality or documentation, remember to update the corresponding SKILL.md file in the appropriate skill directory within the repository (devflow/cli_skills/).


Git Workflow

IMPORTANT: Never commit directly to the main branch. Always create a feature branch before making any commits.

Creating Branches and Pull Requests
  1. Update main branch before creating a new branch:

    git checkout main
    git pull origin main
    

    IMPORTANT: Always ensure your main branch is up-to-date before creating a new feature branch.

  2. Create a branch from the updated main branch:

    git checkout -b <ISSUE-KEY>-<short-description>
    

    Example: git checkout -b proj-12345-fix-validation

  3. Make your changes and commit them to the branch

  4. Push the branch to remote:

    git push -u origin <branch-name>
    
  5. Create a draft PR using auto-discovered PR templates (organization .github repo first, then repository .github/ directory, then user-configured URL, then default template) using gh CLI

Read the full file on GitHub · 1,843 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. 2d ago First seen · 1,843 lines · 19,894 tokens per session scan D cc0d41d0bfef

Subscribe to this mod's changes

devaiflow AGENTS.md is an instructions file published in the GitHub repository itdove/devaiflow (2 stars, last pushed 13d ago), licensed Apache-2.0. It adds 19,894 tokens to every session, about $0.0995 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.