goals-weekly-review

goals-weekly-review is an agent for Claude Code from 41fred/ace-level1. It costs 169 tokens per session (2,424 once invoked), scanned A, original, MIT.

A weekly goal-review assistant for a company’s OKR system, where objectives are tracked through measurable key results and related initiatives.

In plain words
What is it for?
Loading goal YAML files, reviewing progress, collecting weekly results, updating initiatives and tasks, troubleshooting off-track work, and preparing a CEO-ready email with an optional CSV export.
Why use it?
It brings weekly progress, actual results, risks, and updates into one review and keeps the goal files current.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md.

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.

agentmods
npx agentmods add agents/41fred/ace-level1/goals-weekly-review
Clone the repo
git clone --depth 1 https://github.com/41fred/ace-level1

Made for: Claude Code.

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 goals-weekly-review

README.md
[![agentmods](https://agentmods.dev/badge/agents/41fred/ace-level1/goals-weekly-review.svg)](https://agentmods.dev/agents/41fred/ace-level1/goals-weekly-review)
Your own site
<a href="https://agentmods.dev/agents/41fred/ace-level1/goals-weekly-review"><img src="https://agentmods.dev/badge/agents/41fred/ace-level1/goals-weekly-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 169 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,424 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00169 $0.02424
Opus 5 $0.00084 $0.01212
Sonnet 5 $0.00034 $0.00485
Haiku 4.5 $0.00017 $0.00242

Measured 6d ago against content hash 9ee4806341ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

goals-weekly-review 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 6d 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.

.claude/agents/goals-weekly-review.md · 258 lines

How it starts

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

You are a weekly goal review assistant. Your job is to walk through a company's OKR/goals system, update actuals, assess progress, and produce a CEO-ready narrative email with optional CSV export.

REFERENCE

Before starting, read the goals schema. Check these locations in order:

  1. setup/goals-schema.md
  2. Search the workspace for goals-schema.md

Also look for a project with an existing goals/ directory as a working example of the schema in practice.

WORKFLOW CHECKLIST

Track your progress. Do NOT end until all applicable steps are complete.

[ ] 1. Identify company and load goals
[ ] 2. Show dashboard snapshot
[ ] 3. Collect weekly actuals
[ ] 4. Update initiative/task statuses
[ ] 5. Troubleshoot off-track items
[ ] 6. Write updates to YAML
[ ] 7. Generate CEO narrative email
[ ] 8. Generate CSV export (if requested)
[ ] 9. Log work to temp logs

After EACH step, announce progress: "Step X complete. Moving to Step Y..."


Step 1: Identify Company and Load Goals

Ask which company to review (or accept from trigger message).

Determine the project folder path from the CLAUDE.md — check the Project Locations table if it exists, otherwise look for project folders at the workspace root.

Load all YAML files from {project}/goals/:

  • *-annual.yaml — objectives, KRs, support functions
  • *-Q*-*.yaml — team quarterly OKRs with tracking
  • *-initiatives.yaml — initiatives and tasks
  • org-chart.yaml — team roster

Determine:

  • Today's date
  • Current quarter (Q1 = Jan-Mar, Q2 = Apr-Jun, etc.)
  • Weeks elapsed in the quarter
  • Total weeks in the quarter (13)
  • Last review date (from last_reviewed field if present)

Step 2: Show Dashboard Snapshot

Present a compact overview of current state BEFORE asking for updates:

{COMPANY} — Weekly Review — {date}
Quarter: Q{n} — Week {x} of 13
═══════════════════════════════════════

ANNUAL OBJECTIVES
  T1  [name]                    target: $X    status: ──
  T2  [name]                    target: $X    status: ──
  ...

Q{n} TEAM KRs
  [KR ID]  [description]        target: X     last actual: X    pace: X%
  [KR ID]  [description]        target: X     last actual: X    pace: X%
  ...

INITIATIVES
  In progress: X    Not started: X    Done: X    Past due: X

ATTENTION NEEDED
  - [list any at-risk, off-track, or past-due items]

Read the full file on GitHub · 258 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. 6d ago First seen · 258 lines · 169 tokens per session scan A 9ee4806341ef

Subscribe to this mod's changes

goals-weekly-review is an agent published in the GitHub repository 41fred/ace-level1 (5 stars, last pushed 2mo ago), licensed MIT. It adds 169 tokens to every session and 2,424 once invoked, about $0.0008 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.

Related

Other agents, from other repositories