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-notesnpx skills add itdove/devaiflow --skill daf-notesgit 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.00011 | $0.00456 |
| Opus 5 | $0.00005 | $0.00228 |
| Sonnet 5 | $0.00002 | $0.00091 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
daf-notes 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 all notes for the current session in chronological order. This is a READ-ONLY view - it does not modify the session.
daf notes
Auto-detects current session: The command will automatically detect the current Claude Code session and display all notes.
Explicit session lookup:
daf notes PROJ-12345
daf notes my-session
daf notes --latest # Most recently active session
What it shows:
- All notes in chronological order (oldest to newest)
- Timestamp for each note
- JIRA key association (if present)
- Conversation context for multi-conversation sessions
Example output:
Notes for session: implement-backup-feature (PROJ-12345)
### 2025-12-18 10:30:00
Completed API endpoint implementation
### 2025-12-18 14:15:00
Added retry logic with exponential backoff
### 2025-12-18 16:45:00
All tests passing - ready for review
Total: 3 notes
Use this to:
- Review progress history
- Understand what work has been done
- Find specific milestones or decisions
- Prepare status updates
- Refresh context when resuming work
Important notes:
- This is a READ-ONLY command - safe to run inside Claude Code
- Notes are stored in $DEVAIFLOW_HOME/sessions//notes.md
- Notes persist across sessions and exports
- Included in session summaries
- To add notes, use
daf note(works inside Claude sessions)
Related commands:
daf note "Add progress note" # Add note to active session (auto-detects)
daf note PROJ-12345 "Add progress note" # Add note to specific session
daf summary PROJ-12345 # View session summary with notes
daf info PROJ-12345 # View session details
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 · 67 lines · 11 tokens per session scan A b5bb171d0166
daf-notes is a skill published in the GitHub repository itdove/devaiflow (2 stars, last pushed 14d ago), licensed Apache-2.0. It adds 11 tokens to every session and 456 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…
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…
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-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-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.