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 agentmods add agents/41fred/ace-level1/goals-weekly-reviewgit clone --depth 1 https://github.com/41fred/ace-level1Wrote 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/agents/41fred/ace-level1/goals-weekly-review)<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>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.00169 | $0.02424 |
| Opus 5 | $0.00084 | $0.01212 |
| Sonnet 5 | $0.00034 | $0.00485 |
| Haiku 4.5 | $0.00017 | $0.00242 |
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.
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:
setup/goals-schema.md- 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 tasksorg-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_reviewedfield 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]
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.
- 6d ago First seen · 258 lines · 169 tokens per session scan A 9ee4806341ef
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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.