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 commands/zircote-plugins/github-agentic-workflows/aw-dailygit clone --depth 1 https://github.com/zircote-plugins/github-agentic-workflowsWhat 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.00013 | $0.00443 |
| Opus 5 | $0.00006 | $0.00221 |
| Sonnet 5 | $0.00003 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
aw-daily 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.
What it actually says
/aw-daily
Fully autonomous daily pipeline: research the gh-aw ecosystem, post to Discussions, analyze gaps in reference files, implement fixes, create PR to develop, review, and merge. Designed for unattended execution.
Usage
/aw-daily → Full autonomous cycle
/aw-daily --dry-run → Research + gap analysis only, show diff, no commit
/aw-daily --skip-research → Start at gap analysis using latest report
/aw-daily --skip-implementation → Research + gap analysis + issues only, no file edits
/aw-daily --no-merge → Create PR but do not auto-merge
Flags
--dry-run— Run research and gap analysis, show what would change, do not commit or create PR--skip-research— Skip intelligence sweep, start at gap analysis using the most recent report inoutputs/gh-aw-reports/--skip-implementation— Run research, gap analysis, and issue creation, but do not edit files or create PR--no-merge— Create PR but do not auto-merge todevelop
Workflow
You are an autonomous operations agent performing the daily intelligence and update cycle. Execute all phases without user prompting.
Do not prompt the user for input at any point. This command is designed for scheduled unattended execution.
Load the aw-daily skill and execute all phases. The skill handles:
- Pre-flight checks and idempotency
- Intelligence sweep (8 web searches + GitHub activity queries on tracked repos)
- Knowledge base update
- Discussion posting to
project-newscategory - Gap analysis against reference files
- Issue creation for identified gaps
- Implementation on feature branch from
develop - PR creation to
develop - Review and auto-merge
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 · 44 lines · 13 tokens per session scan A 3a44e3e0850f
aw-daily is a command published in the GitHub repository zircote-plugins/github-agentic-workflows (2 stars, last pushed 1mo ago), licensed MIT. It adds 13 tokens to every session and 443 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 commands, from other repositories
discover
Run a full user research cycle — persona creation, empathy mapping, and journey mapping for a product or feature.
test-plan
Run the full usability study workflow — research questions, participant criteria, tasks, metrics, and facilitation guide.
execute
Run the autonomous implementation loop.
review-branch
Review an existing branch holistically before merging — blast radius, conventions, security, and spec compliance.
setup-tools
Detect missing CLI tools and install them to enhance Forge capabilities.
status
Show Forge progress and status.