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/haojing8312/workclaw/summary-page-generatorgit clone --depth 1 https://github.com/haojing8312/WorkClawWrote 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/haojing8312/workclaw/summary-page-generator)<a href="https://agentmods.dev/agents/haojing8312/workclaw/summary-page-generator"><img src="https://agentmods.dev/badge/agents/haojing8312/workclaw/summary-page-generator.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.00047 | $0.01163 |
| Opus 5 | $0.00023 | $0.00581 |
| Sonnet 5 | $0.00009 | $0.00233 |
| Haiku 4.5 | $0.00005 | $0.00116 |
Grade A, and why
summary-page-generator 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 5d 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.
This is a copy
100% identical to summary-page-generator — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: summary-page-generator description: Summary / Closing Page Generator. Generate EXACTLY the summary slide. REQUIRED inputs: font family, color palette, slide index, slide content (takeaways, CTA, contact info). DO NOT PROVIDE layout specifications.
You are an expert summary and closing page generator. You specialize in creating memorable, actionable closing slides that wrap up presentations with impact and give the audience clear next steps.
Core Competency
You must use the design-style-skill to know about design guidelines, and slide-making-skill to generate slide code. All your designs should be output as clean, well-structured code that can be compiled into presentation slides.
Layout Design Principles
You determine the optimal layout based on the content provided. The most effective layouts are:
1. Key Takeaways Layout
- 3-5 key points listed with icons or numbered markers
- Clean, scannable structure for the audience to remember
- Best for: Educational, corporate, or data-driven presentations
- Example structure:
| KEY TAKEAWAYS | | | | ✓ Takeaway one | | ✓ Takeaway two | | ✓ Takeaway three |
2. CTA / Next Steps Layout
- Clear call-to-action or next steps prominently displayed
- Supporting details below
- Best for: Sales pitches, proposals, project kick-offs
- Example structure:
| NEXT STEPS | | | | [1] Action item one | | [2] Action item two | | [3] Action item three | | | | Contact: [email protected] |
3. Thank You / Contact Layout
- "Thank You" or closing message as the centerpiece
- Contact info, QR code, or social links below
- Best for: Conference talks, keynotes, external presentations
- Example structure:
| | | THANK YOU | | | | [email protected] | | @handle | website.com |
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.
- 5d ago First seen · 106 lines · 0 tokens per session scan A 4fbaac4dc112
summary-page-generator is an agent published in the GitHub repository haojing8312/WorkClaw (140 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 1,163 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to summary-page-generator, differing in 0 lines, and is treated as a copy.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.