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 rockyflux/yq-workflow --skill project-daily-summarygit clone --depth 1 https://github.com/rockyflux/yq-workflowWrote 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/rockyflux/yq-workflow/project-daily-summary)<a href="https://agentmods.dev/skills/rockyflux/yq-workflow/project-daily-summary"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/project-daily-summary/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/rockyflux/yq-workflow/project-daily-summary"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/project-daily-summary.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.00085 | $0.01914 |
| Opus 5 | $0.00043 | $0.00957 |
| Sonnet 5 | $0.00017 | $0.00383 |
| Haiku 4.5 | $0.00009 | $0.00191 |
Grade A, and why
project-daily-summary 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 11d 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
project-daily-summary
Summarize today's Codex work by project. Use global Codex session transcripts as the primary evidence source, then enrich with git commits and uncommitted changes. Prioritize plans and final outcomes over process chatter.
Core Rule
Do not produce a chronological 流水账. Do not summarize reasoning noise. Always summarize by project and then by major workstream.
Source Priority
~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl~/.codex/history.jsonl<project>/.specstory/history/if it existsgit log,git status --short,git diff --stat
Important Environment Assumption
In this Codex environment, session transcripts are primarily stored under:
~/.codex/sessions/YYYY/MM/DD/
Do not assume each project stores its own sessions under <project>/.codex/sessions/.
Map sessions back to projects using:
session_meta.payload.cwd- then normalize with
git -C <cwd> rev-parse --show-toplevel - if git root cannot be resolved, fall back to
cwd
Scope
Default scope
Summarize all projects that appear in today's Codex sessions.
If the user provides folders
Summarize only those folders or repositories.
Workflow
Step 1: Determine today's local date
Use the local machine date, not UTC.
Build the session directory path:
~/.codex/sessions/YYYY/MM/DD/
If the directory does not exist, report that no Codex sessions were found for today and stop.
Step 2: Load today's session transcripts
Read all:
rollout-*.jsonl
For each session, extract from the first session_meta line:
- session id
- cwd
- branch
- commit hash
- repository url
- whether it is a subagent session
- parent thread id if present
Step 3: Group by project
For each session:
- Try:
git -C <cwd> rev-parse --show-toplevel - If that fails, use
cwdas the project key.
Output one section per project, not one section per raw session.
Step 4: Handle subagents correctly
What ships with it
1 file 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.
- 11d ago First seen · 309 lines · 85 tokens per session scan A d5ccbe5b8d8f
project-daily-summary is a skill published in the GitHub repository rockyflux/yq-workflow (2 stars, last pushed 2d ago), licensed MIT. It adds 85 tokens to every session and 1,914 once invoked, about $0.0004 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
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
slack-tools
Slack workspace management and automation specialist.
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…