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-jiranpx skills add itdove/devaiflow --skill daf-jiragit clone --depth 1 https://github.com/itdove/devaiflowWrote 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.
[](https://agentmods.dev/skills/itdove/devaiflow/daf-jira)<a href="https://agentmods.dev/skills/itdove/devaiflow/daf-jira"><img src="https://agentmods.dev/badge/skills/itdove/devaiflow/daf-jira.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00021 | $0.01517 |
| Opus 5 | $0.00010 | $0.00758 |
| Sonnet 5 | $0.00004 | $0.00303 |
| Haiku 4.5 | $0.00002 | $0.00152 |
Grade A, and why
daf-jira scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- More reliable than curl commands (automatic auth) How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Alternative Available
If you have a JIRA MCP server configured (e.g., mcp-atlassian), you can use MCP tools directly for JIRA operations.
Quick comparison:
- MCP Tools: Direct API access, advanced operations, full JIRA capabilities
- daf Commands: Validated operations, friendly field names, session integration, team defaults
For complete MCP integration guide, see daf-jira-mcp skill which shows how to:
- Read field mappings and defaults from
daf config show --json(for MCP tools) - Apply DevAIFlow's validation logic manually with MCP tools
- Map friendly field names to JIRA field IDs
- Apply issue type templates
When to use each:
- ✅ Use MCP for: reading tickets, searching, exploring JIRA data
- ✅ Use daf for: creating/updating with validation (auto-applies config, no manual reading needed), session integration, team defaults
Note: daf jira create commands are self-contained - they automatically load configuration, apply validation, and handle field mappings. You do NOT need to read daf config show --json before using daf commands.
View the JIRA ticket associated with the current session in Claude-friendly format.
daf jira view
Auto-detects current session: The command will automatically detect the current Claude Code session and display the associated JIRA ticket details.
Explicit ticket lookup:
daf jira view PROJ-12345
daf jira view PROJ-12345 --history # Include changelog
daf jira view PROJ-12345 --comments # Include comments
daf jira view PROJ-12345 --history --comments # Include both
What it shows:
- Ticket key and summary
- Current status and priority
- Assignee and reporter
- Parent/epic links (if applicable)
- Custom fields (organization-specific)
- Full description
- Acceptance criteria
- Pull request links
- Comments (with
--commentsflag) - Changelog/history (with
--historyflag)
Example output:
Key: PROJ-12345
Summary: Implement customer backup and restore
Status: In Progress
Type: Story
Priority: Major
Assignee: John Doe
Parent: PROJ-59038
Custom Field 1: Value A (custom field)
Custom Field 2: Value B (custom field)
Description:
As a user, I want to backup my data so that I can restore it later.
Acceptance Criteria:
- Backup functionality implemented
- Restore functionality implemented
- Tests added
Why use this:
- More reliable than curl commands (automatic auth)
- Better formatted for Claude to read
- Shows all relevant ticket context
- Consistent with daf tool ecosystem
- Helps understand requirements before coding
Related commands:
daf jira create bug --summary "..." # Create new JIRA bug (validated)
daf jira create story --summary "..." # Create new JIRA story (validated)
daf jira update PROJ-12345 --priority Major # Update ticket fields
Alternative: Use MCP JIRA tools (see daf-jira-mcp skill for validation logic):
mcp__mcp-atlassian__jira_get_issue(issue_key="PROJ-12345")
mcp__mcp-atlassian__jira_create_issue(...)
mcp__mcp-atlassian__jira_update_issue(...)
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.
- 5d ago First seen · 196 lines · 21 tokens per session scan A 92bc2a8b0aa9
daf-jira is a skill published in the GitHub repository itdove/devaiflow (2 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 1,517 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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…
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
content-hash-cache-pattern
Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
load-github-action-thread
Download retained Codex GitHub Action thread artifacts and load their rollout history into the local Codex app. Use when asked to open, load, import, resume, or inspect a Codex automation thread from a GitHub Actions run or a related GitHub issue or pull request.
generating-changelog
Generates polished website release notes between two git tags for docs.streamlit.io. Use when preparing a new Streamlit release or reviewing changes between versions.
composio
Route and complete Composio work across Composio For You and Composio Platform. Use when the user mentions Composio; wants an agent to use apps such as Gmail, Slack, GitHub, Notion, Calendar, or Linear; needs first-time setup, an SDK or MCP integration, CLI operation, migration guidance, current documentation, or help…