week-report-system

week-report-system is a skill for Claude Code, Codex from wangyendt/wayne-skills. It costs 126 tokens per session (1,300 once invoked), scanned A, original, MIT.

A system for preparing weekly work reports from captured conversations, documents, and repository activity. It stores structured material by week and uses that material as the main source for report generation.

In plain words
What is it for?
Use it to capture work notes, plans, experiments, and repository activity, then generate a weekly report from the relevant week's materials.
Why use it?
It keeps report writing tied to recorded work instead of relying only on memory or loose text notes. It also preserves evidence when synchronizing the material fails.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to capture work notes, plans, experiments, and repository activity, then generate a weekly report from the relevant week's materials.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wangyendt/wayne-skills/week-report-system
Install

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.

Any agent
npx skills add wangyendt/wayne-skills --skill week-report-system
Clone the repo
git clone --depth 1 https://github.com/wangyendt/wayne-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for week-report-system

README.md
[![agentmods](https://agentmods.dev/badge/skills/wangyendt/wayne-skills/week-report-system.svg)](https://agentmods.dev/skills/wangyendt/wayne-skills/week-report-system)
Your own site
<a href="https://agentmods.dev/skills/wangyendt/wayne-skills/week-report-system"><img src="https://agentmods.dev/badge/skills/wangyendt/wayne-skills/week-report-system.svg" alt="Measured on agentmods" height="20"></a>
Per session 126 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,300 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00126 $0.01300
Opus 5 $0.00063 $0.00650
Sonnet 5 $0.00025 $0.00260
Haiku 4.5 $0.00013 $0.00130

Measured 8d ago against content hash 4bd2ae8e85ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

week-report-system 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 8d ago.

The scan reads SKILL.md. This mod also ships 3 executable files (scripts/conversation_logger.py, scripts/git_operations.py, scripts/material_ingestor.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

week-report-system/SKILL.md · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Week Report System

Material-first weekly report workflow for work conversations, documents, and recent repository activity.

What This Skill Does

  • Capture work materials into a Git-backed weekly knowledge base
  • Support three material types: conversation, document, repo_activity
  • Generate weekly reports from structured materials, with legacy conversation logs as fallback

Hard Rules

  1. If the user explicitly says 纳入周报素材, 记入周报, 作为周报素材, or equivalent, you must execute material capture.
  2. When generating a weekly report, you must check {year}/week{WW}/materials/ first.
  3. If any readable materials/*.jsonl files exist, the main report analysis must be based on them.
  4. You must not generate a report only from *.txt when structured materials are present.
  5. *.txt digests are a compatibility/debug artifact, not the source of truth.
  6. If Git sync fails after a capture attempt, you must preserve local status evidence.
  7. If one session crosses midnight, captured materials must be split by calendar date in file naming.

Important Boundary

This skill can do best-effort automatic capture only when the host agent actually invokes it.

  • A skill description is not a system-level post-turn hook
  • Do not claim guaranteed logging for every conversation
  • When the user cares about completeness, explicitly ingest materials via scripts/material_ingestor.py

Step 0: First Time — Check Environment

Always run this check first:

echo "USERNAME: ${WEEK_REPORT_GIT_USERNAME:-MISSING}"
echo "TOKEN: $([ -n \"$WEEK_REPORT_GIT_PERSONAL_TOKEN\" ] && echo 'SET' || echo 'MISSING')"
echo "REPO: ${WEEK_REPORT_GIT_REPO:-MISSING}"
  • If all three are set, continue with the request
  • If any is missing, read references/setup_guide.md and guide the user through setup

Determine User Intent

User intent Action
"写周报" / "生成周报" / "本周总结" / "上周周报" Generate report → references/report_generation.md
"把这个纳入周报素材" / "记录这次讨论" Must capture as material → references/material_ingestion.md
"总结这个 plan/experiment 文档并纳入周报" Ingest as document material
"看某个 repo 最近几天提交并纳入周报" Ingest as repo_activity material
"周报系统怎么用" / "怎么设置" / "skill介绍" Show guide → references/user_guide.md
Any other work-related message Answer normally, then best-effort capture a conversation material

Read the full file on GitHub · 108 lines

Changes

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.

  1. 8d ago First seen · 108 lines · 126 tokens per session scan A 4bd2ae8e85ff

Subscribe to this mod's changes

week-report-system is a skill published in the GitHub repository wangyendt/wayne-skills (8 stars, last pushed 12d ago), licensed MIT. It adds 126 tokens to every session and 1,300 once invoked, about $0.0006 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.