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-activenpx skills add itdove/devaiflow --skill daf-activegit 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.00475 |
| Opus 5 | $0.00005 | $0.00237 |
| Sonnet 5 | $0.00002 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
daf-active 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.
What it actually says
Display details about the currently active Claude Code conversation, including session info, branch, and other conversations in the session.
daf active
What it shows:
When a conversation is active:
- Current DAF session name and JIRA key
- Current conversation (working directory)
- Project path
- Git branch
- Goal
- Session status
- Time tracked for this session
- Other conversations in the session
Example output:
┌─ ▶ Currently Active ───────────────────────────────┐
│ DAF Session: PROJ-12345 (#1) │
│ JIRA: PROJ-12345 │
│ Conversation: backend-api │
│ Project: /workspace/backend-api │
│ Goal: Add user profile API and UI │
│ Branch: feature/PROJ-12345 │
│ Time (this session): 1h 23m │
│ Status: in_progress │
│ │
│ Other conversations in this session: │
│ • frontend-app (branch: feature/PROJ-12345-ui) │
└────────────────────────────────────────────────────┘
To pause: Exit Claude Code
When no active conversation:
No active conversation
Recent conversations:
PROJ-12345#1 (backend) - paused 15m ago
PROJ-12346#1 (frontend) - paused 2h ago
Use this to:
- Verify which conversation is currently active
- See which git branch you're working on
- Check which project you're in
- View other conversations in the session
- Find recently paused conversations
Why this matters for multi-conversation sessions:
- Each conversation has its own git repository and branch
- Making changes in the wrong conversation can cause lost work
- Use
daf activeto confirm you're in the right project before coding
Related commands:
/daf list-conversations # See all conversations in session
/daf info # Detailed session information
daf list --active # List all active sessions
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.
- 2d ago First seen · 71 lines · 10 tokens per session scan A e11278f526fb
daf-active 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 475 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
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…
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…
meridian-etl
Debug and work with Meridian's ETL pipeline. Covers session boundary detection, cursor management, DB queries, and common failure modes.
meridian-mcp
Build, configure, and debug the Meridian MCP server. Exposes app session data to AI tools via the Model Context Protocol.
github-image-upload
Upload local images and other files (PDF, zip, log, …) to GitHub and embed them in a pull request description, an issue, or a comment — producing canonical github.com/user-attachments URLs (private-repo uploads stay private). Use when asked to "attach a screenshot to the PR", "add an image to the PR description", "put…
session-summary
You summarise ONE work-burst of a developer's coding-agent session. The goal is to capture what the developer actually worked on, and why it mattered, so that a PM, a teammate, or the developer themselves can immediately understand the purpose and the outcome at a glance — without reading the transcript.