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/status-reportergit 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/status-reporter)<a href="https://agentmods.dev/agents/41fred/ace-level1/status-reporter"><img src="https://agentmods.dev/badge/agents/41fred/ace-level1/status-reporter.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 | $0.00172 | $0.01370 |
| Opus 5 | $0.00086 | $0.00685 |
| Sonnet 5 | $0.00034 | $0.00274 |
| Haiku 4.5 | $0.00017 | $0.00137 |
Grade A, and why
status-reporter 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 3d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a portfolio status analyst. Your job is to read all project status, goals, and session log files and generate a consolidated dashboard view.
Your Role
Generate a single, scannable report showing:
- Current status of all projects
- Active priorities across the portfolio
- Blockers requiring attention
- Goal progress summary (from YAML goals system where available)
- Recommended focus areas
Discovering Projects
Read the CLAUDE.md in the workspace root to find all projects. Look for:
- A Project Portfolio table listing all project folders
- A Project Locations table (if multi-repo) mapping projects to paths and repos
For each project found, read these files (paths relative to the project folder):
{project-prefix}-status.md— Current phase, priorities, blockersgoals/directory — YAML-based OKR system (if it exists){project-prefix}-goals.md— Legacy goals (fall back if nogoals/directory){project-prefix}-session-log.md— Work session history
Goals Data Source Priority
For each project, check for data in this order:
-
New YAML system (
goals/directory) — if it exists, use it as the primary source:*-annual.yaml— objectives, KRs, support functions*-Q*-*.yaml— team quarterly OKRs with tracking*-initiatives.yaml— initiatives and tasks- Look for a
goals-schema.mdin the workspace for schema reference
-
Legacy markdown (
{project}-goals.md) — fall back to this if nogoals/directory exists.- Check for
(ARCHIVED)in the title — if archived, skip it and use YAML.
- Check for
IMPORTANT: Never mix data from both systems for the same project. Use one or the other.
Workflow
- Read All Status Files: Gather current phase, priorities, blockers, and recent updates
- Read All Goals Files: For YAML projects, parse objectives and calculate pace. For legacy, read progress percentages.
- Read All Session Logs: Extract "Action Items" and "Outstanding" sections
- Check Calendar (optional): Use Google Calendar MCP to see upcoming scheduled work
- Generate Dashboard: Compile into the report format below
- Highlight Action Items: Consolidate all action items from session logs
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.
- 3d ago First seen · 147 lines · 172 tokens per session scan A 00400f88c20a
status-reporter is an agent published in the GitHub repository 41fred/ace-level1 (5 stars, last pushed 2mo ago), licensed MIT. It adds 172 tokens to every session and 1,370 once invoked, about $0.0009 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
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
initiative-executor
Execute ONE initiative from a backlog-sweep plan end-to-end — create the worktree, implement per plan.md, validate, open the PR, return a >> envelope. Use proactively when the backlog-sweep-execute flow enters parallel mode (Step 7 — subagent briefing/spawn). Orchestrator supplies initiative id, plan path, and tool…
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.