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.
npx agentmods add skills/itdove/devaiflow/daf-helpnpx skills add itdove/devaiflow --skill daf-helpgit clone --depth 1 https://github.com/itdove/devaiflowWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00010 | $0.00426 |
| Opus 5 | $0.00005 | $0.00213 |
| Sonnet 5 | $0.00002 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
daf-help 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.
What it actually says
Display a quick reference of commonly used daf commands.
daf --help
Core Session Commands:
During work:
daf status # Check progress dashboard
daf active # Show currently active conversation
daf list # List all sessions
JIRA Integration:
daf jira view PROJ-12345 --comments # View ticket details with comments
daf jira create bug --summary "..." # Create new JIRA bug
daf jira create story --summary "..." # Create new JIRA story
daf jira update PROJ-12345 --priority Major # Update ticket
Multi-Conversation Sessions:
/daf list-conversations # List all conversations in session
/daf read-conversation # Read work done in other repositories
Configuration:
daf config show # View current configuration
daf skills # List all available skills
daf skills <skill-name> # Inspect specific skill
Getting Help:
daf --help # Main help
daf <command> --help # Command-specific help
daf jira create bug --help # See available options
Quick Reference:
- Session = work on one JIRA ticket
- Conversation = work in one repository
- Multi-conversation = one session across multiple repos (default)
- Multi-session = separate approaches to same ticket (use
--new-session)
Common Workflows:
Multi-repo feature:
# Work in current repository
/daf read-conversation # Read work from other repositories in this session
# ... work in current repository with context from other repos ...
Full documentation:
- Commands: See docs/07-commands.md
- Workflows: See docs/14-workflows.md
- Troubleshooting: See docs/11-troubleshooting.md
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.
- yesterday First seen · 69 lines · 10 tokens per session scan A 001a8b2ba795
daf-help is a skill published in the GitHub repository itdove/devaiflow (2 stars, last pushed 13d ago), licensed Apache-2.0. It adds 10 tokens to every session and 426 once invoked, about $0.0001 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.
Other skills, from other repositories
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…
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.
jira-issue-management
Core JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile)…
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.
jira-issue-relationships
Issue linking, blockers, and dependency analysis. TRIGGERS: 'what's blocking', 'what is blocking', 'is blocked by', 'link issues', 'link to', 'blockers for', 'depends on', 'clone issue', 'clone with', 'blocking chain', 'dependency graph', 'show dependencies', 'get blockers', 'relates to', 'duplicates'. Use for issue…
jira-search-jql
Find issues by criteria (status, assignee, priority, etc.) using JQL. Create filters, export results to CSV/JSON, bulk update. Ideal for reporting and automation.