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 skills add zircote-plugins/github-agentic-workflows --skill aw-dailygit clone --depth 1 https://github.com/zircote-plugins/github-agentic-workflowsWrote 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/zircote-plugins/github-agentic-workflows/aw-daily)<a href="https://agentmods.dev/skills/zircote-plugins/github-agentic-workflows/aw-daily"><img src="https://agentmods.dev/badge/skills/zircote-plugins/github-agentic-workflows/aw-daily/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zircote-plugins/github-agentic-workflows/aw-daily"><img src="https://agentmods.dev/badge/skills/zircote-plugins/github-agentic-workflows/aw-daily.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00094 | $0.03220 |
| Opus 5.5 | $0.00038 | $0.01288 |
| Sonnet 5.5 | $0.00019 | $0.00644 |
| Haiku 4.5 | $0.00009 | $0.00322 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 375 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous Daily Intelligence Pipeline
You are an autonomous operations agent. Execute all phases below in order. If any phase fails, follow the error mode specified. Do not prompt the user for input at any point. This pipeline is designed for fully unattended execution.
Parse the argument string for optional flags:
--dry-run-- Research + gap analysis only, show diff, do not commit or PR--skip-research-- Start at Phase 4 using the latest report inoutputs/gh-aw-reports/--skip-implementation-- Research + gap analysis + issues only, do not edit files or PR--no-merge-- Create PR but do not auto-merge todevelop
Phase 0: Pre-flight & Idempotency
- Determine today's date:
date +%Y-%m-%d-> store asTODAY - Verify
ghCLI:gh auth status - Verify clean working tree:
git status --porcelainmust be empty- If dirty: ABORT -- "Working tree is dirty. Commit or stash before running /aw-daily."
- Capture current branch:
git branch --show-current-> store asORIGINAL_BRANCH
Ensure develop branch exists:
if ! git ls-remote --exit-code origin develop >/dev/null 2>&1; then
git checkout main
git checkout -b develop
git push -u origin develop
git checkout "$ORIGINAL_BRANCH"
fi
git fetch origin develop
Idempotency checks:
- Check if today's Discussion already exists:
EXISTING_DISCUSSION=$(gh api graphql -f query='{ repository(owner:"zircote", name:"github-agentic-workflows") { discussions(categoryId:"DIC_kwDORSXBr84C61Lr", first:5, orderBy:{field:CREATED_AT, direction:DESC}) { nodes { title url } } } }' -q ".data.repository.discussions.nodes[] | select(.title | contains(\"$TODAY\")) | .url")
If found and --skip-research not set: set RESEARCH_DONE=true, store URL as DISCUSSION_URL
- Check if today's PR already exists:
EXISTING_PR=$(gh pr list --repo zircote/github-agentic-workflows --base develop --search "daily-intelligence-$TODAY" --state all --json number,url -q '.[0].url')
If found: report "Today's pipeline already completed. PR: $EXISTING_PR" and exit successfully.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 375 lines · 94 tokens per session scan A 8a0f14f493ad
aw-daily is a skill published in the GitHub repository zircote-plugins/github-agentic-workflows (2 stars, last pushed 3mo ago), licensed MIT. It adds 94 tokens to every session and 3,220 once invoked, about $0.0004 per session on Opus 5.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
github-release-management
Use when cutting a GitHub release that needs progressive canary rollout (5%→25%→50%→100%) with automated health gates and auto-rollback on error-rate or latency regressions.
pr-review-triage
Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.
dependency-triage
Scan package manifests and lockfiles for outdated and vulnerable dependencies. Classify by severity and update type.
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
output-standards
Use this skill when defining or enforcing output formatting standards for agent responses in WrongStack. Triggers: user says "next steps format", "output standard", "response format", "final message format", "standardize next steps".
web-platform-baseline
Use this skill before asserting that a CSS, HTML or accessibility capability is available, unavailable, or the right tool — it carries dated, refreshable platform facts and refuses to let stale knowledge be stated as current. Triggers: user says "container query", "can I use", "browser support", "modern CSS", ":has"…