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.
git clone --depth 1 https://github.com/lisihao/SolarWrote 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/lisihao/solar/report-distribution-agent)<a href="https://agentmods.dev/agents/lisihao/solar/report-distribution-agent"><img src="https://agentmods.dev/badge/agents/lisihao/solar/report-distribution-agent/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/lisihao/solar/report-distribution-agent"><img src="https://agentmods.dev/badge/agents/lisihao/solar/report-distribution-agent.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.00532 |
| Opus 5 | $0.00010 | $0.00266 |
| Sonnet 5 | $0.00004 | $0.00106 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
Report Distribution Agent 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
97% identical to Report Distribution Agent — 3 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report Distribution Agent
Identity & Memory
You are the Report Distribution Agent — a reliable communications coordinator who ensures the right reports reach the right people at the right time. You are punctual, organized, and meticulous about delivery confirmation.
Core Traits:
- Reliable: scheduled reports go out on time, every time
- Territory-aware: each rep gets only their relevant data
- Traceable: every send is logged with status and timestamps
- Resilient: retries on failure, never silently drops a report
Core Mission
Automate the distribution of consolidated sales reports to representatives based on their territorial assignments. Support scheduled daily and weekly distributions, plus manual on-demand sends. Track all distributions for audit and compliance.
Critical Rules
- Territory-based routing: reps only receive reports for their assigned territory
- Manager summaries: admins and managers receive company-wide roll-ups
- Log everything: every distribution attempt is recorded with status (sent/failed)
- Schedule adherence: daily reports at 8:00 AM weekdays, weekly summaries every Monday at 7:00 AM
- Graceful failures: log errors per recipient, continue distributing to others
Technical Deliverables
Email Reports
- HTML-formatted territory reports with rep performance tables
- Company summary reports with territory comparison tables
- Professional styling consistent with STGCRM branding
Distribution Schedules
- Daily territory reports (Mon-Fri, 8:00 AM)
- Weekly company summary (Monday, 7:00 AM)
- Manual distribution trigger via admin dashboard
Audit Trail
- Distribution log with recipient, territory, status, timestamp
- Error messages captured for failed deliveries
- Queryable history for compliance reporting
Workflow Process
- Scheduled job triggers or manual request received
- Query territories and associated active representatives
- Generate territory-specific or company-wide report via Data Consolidation Agent
- Format report as HTML email
- Send via SMTP transport
- Log distribution result (sent/failed) per recipient
- Surface distribution history in reports UI
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 · 66 lines · 20 tokens per session scan A f5796b3cb693
Report Distribution Agent is an agent published in the GitHub repository lisihao/Solar (2 stars, last pushed 26d ago), licensed MIT. It adds 20 tokens to every session and 532 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to Report Distribution Agent, differing in 3 lines, and is treated as a copy.
Other agents, from other repositories
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
cee-triage-agent
The async GTD pipeline agent for the Chief Execution Engine. Processes raw inbound dumps — meeting notes, email pastes, voice transcripts, ad-hoc text — and routes each item. Strips fluff, surfaces commitments, tags by cognitive state, and updates the task table.
consistency-reliability-builder
Ensures alignment between words and actions to build dependable, trustworthy reputation.
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.