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 cnfeat/top-pm-skills --skill engineering-weekly-reportgit clone --depth 1 https://github.com/cnfeat/top-pm-skillsWrote 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/cnfeat/top-pm-skills/engineering-weekly-report)<a href="https://agentmods.dev/skills/cnfeat/top-pm-skills/engineering-weekly-report"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/engineering-weekly-report/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/cnfeat/top-pm-skills/engineering-weekly-report"><img src="https://agentmods.dev/badge/skills/cnfeat/top-pm-skills/engineering-weekly-report.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.00069 | $0.02069 |
| Opus 5 | $0.00034 | $0.01035 |
| Sonnet 5 | $0.00014 | $0.00414 |
| Haiku 4.5 | $0.00007 | $0.00207 |
Grade A, and why
engineering-weekly-report 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 7d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Engineering Weekly Report
Produce a weekly engineering status report that a team can send to stakeholders, their engineering manager, and the team itself. The format is fixed week-over-week so readers know exactly where to look — shipping progress at the top, decisions in the middle, risks and next steps at the bottom. The report must be readable in under 2 minutes. Avoid prose walls: use bullet points, status tags, and short tables. If metrics are not provided, leave the metrics section with [data needed] markers rather than fabricating numbers.
Required Inputs
Ask for these if not already provided:
- Team name and report period — team name plus week number or date range (e.g., "Platform Team, Week 21, May 12–16")
- Work items shipped this week — what was completed and released or merged
- Work items in progress — what is actively being worked on, with rough percent-complete if known
- Blocked items — what is blocked, who owns the block, and what is needed to unblock
- Key decisions made — any architecture, process, or priority decisions made this week
- Decisions needed next week — any decisions that need to be made soon and who needs to make them
- Risks and escalations — anything that threatens next week's commitments or needs leadership visibility
- Next week's top priorities — the 3–5 things the team plans to accomplish next week
Optional but useful:
- Key metrics — reliability (error rate, p99 latency), velocity (story points completed), or other health indicators
- Team health notes — PTO, new joins, attrition, morale signals worth noting
- Sprint or iteration number — if the team runs sprints
Output Format
Engineering Weekly Report — [Team Name]
Week: [Week Number] | [Date Range, e.g., May 12–16, 2025] Author: [Name or Team Lead] Distribution: [e.g., Eng leadership, Product, Team]
Shipping Progress
Shipped This Week
| Item | Description | Impact |
|---|---|---|
| [Feature / Fix / Infra change] | [One-line description] | [Who benefits / what it unblocks] |
| [Feature / Fix / Infra change] | [One-line description] | [Who benefits / what it unblocks] |
| [Feature / Fix / Infra change] | [One-line description] | [Who benefits / what it unblocks] |
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.
- 7d ago First seen · 173 lines · 69 tokens per session scan A 5d1f38108adf
engineering-weekly-report is a skill published in the GitHub repository cnfeat/top-pm-skills (48 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 2,069 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.