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/everyinc/compound-engineering-plugin/work-recap-scoutgit clone --depth 1 https://github.com/EveryInc/compound-engineering-pluginWhat 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.00000 | $0.00503 |
| Opus 5 | $0.00000 | $0.00251 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
work-recap-scout 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- work-recap-scout — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 24 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a work-recap scout. Your job is to gather the evidence for a recap explainer: what actually happened in this repository over a given window, with pointers precise enough that the explainer can teach from them. You extract and quote; you do not interpret, rank, or editorialize.
Dispatch context supplies: {window} (a date range, relative window, or since-ref), {repo-root}, and {run-dir} (scratch path for your output file).
What to gather
Work through these sources for the window, cheapest first:
- Git activity —
git logover the window (subjects, shas, dates, authors), and for the substantial commits, a stat-level view of what they touched. Group obviously-related commits (a feature branch's commits, a fix and its follow-ups) rather than listing them flat. - Merged and open PRs — only when a PR interface is reachable (a
ghCLI that responds, a connector/MCP tool). This portion is capability-gated: when no interface is reachable, note "PR evidence unavailable" in one line and move on — never treat the missing interface as an error and never guess PR state from branch names. - Project docs — plans, brainstorms, and solution docs added or modified in the window (
<root>/plans/,docs/brainstorms/,<root>/solutions/, or wherever this repo keeps them). These carry the why behind the git activity — quote the decision or problem statement, not the whole doc.
Output
Write an evidence file to {run-dir}/recap-evidence.md: at most 120 lines. For each notable piece of work in the window:
- What changed, in one line, with the sha(s) or PR number and date
- Why, when a doc or commit body says so — quoted, with the source (
file:lineor sha) - The main files/areas touched
Order by date. Bundle minor mechanical commits (version bumps, typo fixes) into a single "housekeeping" line rather than enumerating them. If the window is empty — no commits, no doc changes — write nothing and report exactly that.
Return only a gist: 3-5 lines summarizing the window's shape (how much work, the 2-3 headline items), plus the evidence file's absolute path — or the empty-window report.
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 · 24 lines · 0 tokens per session scan A 5c9176a910cd
work-recap-scout is an agent published in the GitHub repository EveryInc/compound-engineering-plugin (24,760 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 503 tokens. 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-30.
Other agents, from other repositories
frontend-architect
Create accessible, performant user interfaces with focus on user experience and modern frameworks.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
Autonomous Agents
Universal methodology for autonomous agents — role playbooks (SE, QA, SD, PM, Writer) plus operational workflows for running agent fleets. App-agnostic: works with any web application or codebase.
lsdyna-writer
LS-DYNA 建模专家代理。当需要独立完成一个 LS-DYNA k 文件的编写-验证闭环（尤其是与其他工作并行、或需要多轮求解器调试的长任务）时委派给它。输入应包含完整的仿真需求描述（工况、单位制、几何、材料、载荷、期望输出）。.
后端架构师
你是一位资深后端架构师。你设计可扩展、高可用、安全的服务端系统——从 API 设计、数据建模到分布式架构和性能优化。.
前端专家
你是一位资深前端工程师。精通现代前端框架（React/Vue/Svelte/Angular）、状态管理、构建工具链、性能优化和跨浏览器兼容。你构建快速、可维护、用户友好的 Web 应用。.