daf-workflow

A session-context workflow for DevAIFlow, a development work-management system. It reads the current session details, related issue-tracker ticket, and project context files before work begins.

In plain words
What is it for?
Check a DevAIFlow session, load its goal and metadata, read linked GitHub, GitLab, or Jira tickets, and guide commands such as opening, creating, or investigating work.
Why use it?
It prevents an agent from working without knowing the task, project location, branch, or prior discussion. When no managed session is active, it provides a separate guide for working on its own.

Skill for Claude CodeCodex

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 skills/itdove/devaiflow/daf-workflow
Any agent
npx skills add itdove/devaiflow --skill daf-workflow
Clone the repo
git clone --depth 1 https://github.com/itdove/devaiflow

Made for: Claude Code, Codex.

Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,509 The whole file, excluding the scripts and references it only reads on demand.
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.00068 $0.02509
Opus 5 $0.00034 $0.01255
Sonnet 5 $0.00014 $0.00502
Haiku 4.5 $0.00007 $0.00251

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

Security

Grade A, and why

daf-workflow 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.

devflow/cli_skills/daf-workflow/SKILL.md · 282 lines

How it starts

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

DevAIFlow Session Context

Run this command to check the session environment:

echo "DAF_SESSION_NAME=$DAF_SESSION_NAME" "DAF_COMMAND=$DAF_COMMAND"

Important: Use this command exactly as written — the text must match the agent's permission pattern. Do not rephrase or restructure.

If DAF_SESSION_NAME is set (non-empty), this is a managed DevAIFlow session — follow the initialization steps below. If empty, skip to the Standalone Workflow Guide section at the bottom.


Session Initialization

When DAF_SESSION_NAME is set, perform these steps before doing any other work:

1. Read Session Metadata

daf info $DAF_SESSION_NAME

This shows: session name, goal, issue key, status, working directory, branch, workspace, session type, and conversation history.

2. Read Issue Tracker Ticket

If daf info shows an issue key (e.g., owner/repo#123 or PROJ-456), read the ticket using that key:

# For GitHub issues (use the issue number from daf info)
gh issue view <number> --comments

# For GitLab issues
glab issue view <number> --comments

# For JIRA tickets (use the issue key from daf info)
daf jira view <issue_key> --comments

Replace <number> or <issue_key> with the actual value shown in daf info output.

3. Read Context Files

First, discover the DevAIFlow config directory:

CONFIG_DIR=$(daf config show --paths | grep config_dir | cut -d= -f2)

Then read the hierarchical context files if they exist in CONFIG_DIR:

  • CONFIG_DIR/ENTERPRISE.md (enterprise-wide policies and standards)
  • CONFIG_DIR/ORGANIZATION.md (organization coding standards)
  • CONFIG_DIR/TEAM.md (team conventions and workflows)
  • CONFIG_DIR/USER.md (personal notes and preferences)

4. Read Skill Files

Using the same CONFIG_DIR from Step 3, check for additional skills:

  • CONFIG_DIR/.claude/skills/ (enterprise/organization/team/user skills)
  • Project-level skills in the project's .claude/skills/ directory

Read the full file on GitHub · 282 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 · 282 lines · 68 tokens per session scan A dcafedda4695

Subscribe to this mod's changes

daf-workflow is a skill published in the GitHub repository itdove/devaiflow (2 stars, last pushed 13d ago), licensed Apache-2.0. It adds 68 tokens to every session and 2,509 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

workingon

Record the work done in this Claude Code session in the configured ticketing tool (Jira, Linear, GitHub Issues, Trello or Vikunja), creating the ticket, adding a short progress comment, linking an existing one or closing it. Use it when the [workingon] hook reports unrecorded work, when the user types /workingon, and…

oliverjueguen/workingon-claude-skill · 92 tokens

workingon

Record the work done in this Claude Code session in the configured ticketing tool (Jira, Linear, GitHub Issues, Trello or Vikunja), creating the ticket, adding a short progress comment, linking an existing one or closing it. Use it when the [workingon] hook reports unrecorded work, when the user types /workingon, and…

oliverjueguen/workingon-claude-skill · 92 tokens

pir-action-tracker

Parses Post-Incident Review (PIR) pages in a Confluence space, fetches live status from referenced Jira tickets, updates action item tables with current status and due dates, marks completed PIRs with a visual closure panel, and surfaces any overdue actions for follow-up. Designed for Customer Success, Support, and…

Perseus-Computing-LLC/perseus · 78 tokens

jira-administration

Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.

grandcamel/JIRA-Assistant-Skills · 51 tokens

jira-service-management

Complete ITSM/ITIL workflow support for JSM - service desks, requests, SLAs, customers, approvals, knowledge base. Use when managing service desk requests, tracking SLAs, or handling customer operations.

grandcamel/JIRA-Assistant-Skills · 47 tokens

jira-time-tracking

Time tracking, worklogs, and time reports. TRIGGERS: 'log time', 'time spent on', 'log hours', 'log work', 'worklog', 'time tracking', 'timesheet', 'how much time', 'time logged', 'time report', 'export timesheet', 'set estimate', 'remaining estimate', 'original estimate'. Use for time-related queries and operations…

grandcamel/JIRA-Assistant-Skills · 121 tokens