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-gitnpx skills add itdove/devaiflow --skill daf-gitgit 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.00026 | $0.03071 |
| Opus 5 | $0.00013 | $0.01536 |
| Sonnet 5 | $0.00005 | $0.00614 |
| Haiku 4.5 | $0.00003 | $0.00307 |
Grade A, and why
daf-git 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.
How it starts
The opening of the file, as written. The whole thing — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Complete workflow for managing GitHub Issues and GitLab Issues in DevAIFlow. Automatically detects the platform from your git repository.
Quick Start
View issue details (use gh/glab CLI directly):
# GitHub
gh issue view 123
gh issue view 123 --comments
# GitLab
glab issue view 123
glab issue view 123 --comments
All Commands
Creating Issues
Use gh or glab CLI directly to create issues, then link to your session:
# GitHub
gh issue create --title "Add caching" --body "Description here" --label "enhancement"
# Then link to session:
daf link <issue_url>
# GitLab
glab issue create --title "Add caching" --description "Description here" --label "enhancement"
# Then link to session:
daf link <issue_url>
Issue Body Templates
When creating issues with daf git new, templates are automatically injected into the prompt.
Templates come from (in priority order):
- Config templates -
github_issue_templatesin organization.json/team.json - Repo templates -
.github/ISSUE_TEMPLATE/(GitHub) or.gitlab/issue_templates/(GitLab) - Built-in defaults - Standard templates for bug, enhancement, task, epic
Example structured issue body (bug):
## Bug Description
**What happened:**
API returns 500 when pagination limit exceeds 100
**Expected behavior:**
API should return 400 with validation error
**Steps to reproduce:**
1. Call GET /api/items?limit=200
2. Observe 500 Internal Server Error
## Environment
- Version: v2.3.1
- OS: Linux
## Acceptance Criteria
- [ ] Bug is fixed
- [ ] Regression test added
- [ ] No new issues introduced
Configuring custom templates in organization.json or team.json:
{
"github_issue_templates": {
"bug": "## Bug Report\n\n**Symptoms:**\n...",
"enhancement": "## Feature Request\n\n**Problem:**\n...",
"task": "## Task\n\n**Objective:**\n..."
}
}
Viewing Issues
Use the gh or glab CLI directly to view issues:
# GitHub
gh issue view 123 # View issue
gh issue view 123 --comments # Include comments
gh issue view 123 -R owner/repo # Cross-repo
# GitLab
glab issue view 123 # View issue
glab issue view 123 --comments # Include comments
glab issue view 123 -R owner/repo # Cross-repo
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 · 430 lines · 26 tokens per session scan A 3cf1c7ab0162
daf-git is a skill published in the GitHub repository itdove/devaiflow (2 stars, last pushed 13d ago), licensed Apache-2.0. It adds 26 tokens to every session and 3,071 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.