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-statusnpx skills add itdove/devaiflow --skill daf-statusgit 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.00008 | $0.00508 |
| Opus 5 | $0.00004 | $0.00254 |
| Sonnet 5 | $0.00002 | $0.00102 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
daf-status 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 3d 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 progress, ticket status breakdown, and time tracking summary.
daf status
What it shows:
Overview (when grouping configured):
- Grouping information (configured via organization.json)
- Totals breakdown if configured (configured via organization.json)
- Total time tracked
- Progress metrics
Tickets by Status:
- In Progress: Active tickets being worked on
- Paused: Temporarily stopped tickets
- Created: New tickets not yet started
- Complete: Finished tickets
Example output (with grouping configured):
Group: Value-A
Progress: 8/26 (totals field)
In Progress:
🐛 PROJ-12345 (PROJ-12345) Fix password reset | 1h 20m
└─ backend-api | Last: 2025-01-25 14:30
📋 PROJ-12346 (PROJ-12346) Add 2FA support | 2h 15m
└─ frontend | Last: 2025-01-25 15:00
Complete:
📋 PROJ-12343 (PROJ-12343) Login endpoint | 2h 30m
└─ backend-api | Last: 2025-01-24 16:00
Summary
Total sessions: 3
In progress: 2
Complete: 1
Total time tracked: 6h 5m
Use this to:
- Check progress at a glance
- See which tickets need attention
- Track time spent
- Report status in standups
- Plan daily work priorities
Filter sessions by custom fields:
daf list --field <field_name>=<value> # Filter by custom field name
daf list --field grouping_field="Value A" # Uses field name from field_mappings
daf list --field status_field="In Progress" # Field names configured in organization.json
Note: Custom field names must be defined in your organization.json field_mappings configuration.
Related commands:
daf list --active # List only active sessions
daf time PROJ-12345 # Detailed time tracking for ticket
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.
- 3d ago First seen · 71 lines · 8 tokens per session scan A 1e5316983788
daf-status is a skill published in the GitHub repository itdove/devaiflow (2 stars, last pushed 14d ago), licensed Apache-2.0. It adds 8 tokens to every session and 508 once invoked, about $0.0000 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.