Borrowing it
Nothing to install: this file belongs to lucasviola/specwiki. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/lucasviola/specwiki/main/.agents/skills/specwiki-daily-summary/SKILL.mdgit clone --depth 1 https://github.com/lucasviola/specwikiWrote 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/lucasviola/specwiki/specwiki-daily-summary)<a href="https://agentmods.dev/skills/lucasviola/specwiki/specwiki-daily-summary"><img src="https://agentmods.dev/badge/skills/lucasviola/specwiki/specwiki-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/lucasviola/specwiki/specwiki-daily-summary"><img src="https://agentmods.dev/badge/skills/lucasviola/specwiki/specwiki-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.00063 | $0.01390 |
| Opus 5.5 | $0.00025 | $0.00556 |
| Sonnet 5.5 | $0.00013 | $0.00278 |
| Haiku 4.5 | $0.00006 | $0.00139 |
Grade A, and why
specwiki-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 2mo 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
specwiki Daily Summary
Goal: Produce an accurate, readable recap of work completed today — not a generic status report.
Conventions
{project-root}= workspace root (specwiki repo)- Default date: today from
user_info(respect the user's timezone when choosing calendar day) - Override date when the user says e.g. "yesterday" or gives an explicit date (
YYYY-MM-DD)
Workflow
Step 1 — Gather data (parallel)
Run these in parallel:
# Commits for the target date (adjust DATE)
DATE=$(date +%Y-%m-%d) # or user-specified date
git log --since="${DATE} 00:00:00" --until="${DATE} 23:59:59" --format="%h %ad %s" --date=format:"%H:%M"
git log --since="${DATE} 00:00:00" --until="${DATE} 23:59:59" --format="%h|%s"
# Working tree
git status --short
# Optional one-shot gather script
bash {project-root}/.agents/skills/specwiki-daily-summary/scripts/gather-daily-data.sh {project-root} "${DATE}"
Also read:
| Source | Path | Purpose |
|---|---|---|
| Sprint status | {project-root}/_bmad-output/implementation-artifacts/sprint-status.yaml |
Epic/story states, last_updated |
| Package version | {project-root}/package.json |
Current release version |
| Deferred work | {project-root}/_bmad-output/implementation-artifacts/deferred-work.md |
Only if commits touch it |
For feature commits (feat, fix, major docs), run git show --stat <hash> to see scope. Do not stat every commit — focus on non-chore commits and version bumps.
Step 2 — Map commits to stories
Parse commit subjects for story/epic hints:
(S21.6),(E21 S21.3),S16.5,epic-21,21-3-*in messages or changed story filenames- Story files under
_bmad-output/implementation-artifacts/namedN-M-*.md
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.
- 2mo ago First seen · 155 lines · 63 tokens per session scan A 743591b6fb85
specwiki-daily-summary is a skill published in the GitHub repository lucasviola/specwiki (12 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 1,390 once invoked, about $0.0003 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-30.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.