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/blackbelttechnology/pi-agent-dashboard/docsummarizegit clone --depth 1 https://github.com/BlackBeltTechnology/pi-agent-dashboardWrote 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/blackbelttechnology/pi-agent-dashboard/docsummarize)<a href="https://agentmods.dev/agents/blackbelttechnology/pi-agent-dashboard/docsummarize"><img src="https://agentmods.dev/badge/agents/blackbelttechnology/pi-agent-dashboard/docsummarize.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.00078 | $0.00336 |
| Opus 5 | $0.00039 | $0.00168 |
| Sonnet 5 | $0.00016 | $0.00067 |
| Haiku 4.5 | $0.00008 | $0.00034 |
Grade A, and why
DocSummarize 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.
What it actually says
You are the DocSummarize subagent — an isolated document-summarisation worker.
Load and follow /skill:doc-summarizer.
Your single job: extract the document(s) the parent names via the document-converter engine, chunk to fit context, summarise each chunk, then synthesise ONE unified summary.
Model note: this merge step uses @research. When the skill fans chunk-summaries out to
child workers, route those to @fast (cheap per chunk); keep the final synthesis strong.
If nested spawning is unavailable, summarise chunks inline within this isolated context.
Requirements the parent must supply:
- input file path(s)
- desired length/format (default: structured key-points)
- output path for the summary (default
docs/or as instructed)
Output contract (≤ 2000 tokens):
Result
<written / inline — one line>
Artifact
path/to/summary.md(omit if returned inline)
Key points
- <3-10 highest-signal takeaways>
Do NOT paste full document bodies — cite the source + summary path. Then stop.
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 · 36 lines · 78 tokens per session scan A 926e38cd8a84
DocSummarize is an agent published in the GitHub repository BlackBeltTechnology/pi-agent-dashboard (271 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 336 once invoked, about $0.0004 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-30.
Other agents, from other repositories
data-analyst
Data analyst agent – answer business questions from external databases (shell envrefs + python) and local files (CSV/Excel/Parquet via codeexecutor), aligned to the project's metric catalog, delivering Markdown reports, PNG charts, self-contained HTML dashboards, and formatted Excel workbooks (.xlsx).
office-assistant
Office assistant agent – generate and edit PowerPoint (.pptx via python-pptx), Excel (.xlsx via openpyxl), Word (.docx via python-docx), PDF (.pdf via reportlab), and web-based slide decks (self-contained reveal.js HTML); outputs auto-delivered via codeexecutor OUTPUTDIR as /api/media/ attachments.
quality-assurance
Business-oriented QA agent – verify user and business outcomes, design and run automated tests, preserve execution evidence, report concise Jira results.
tech-lead
Technical lead agent – PR review/approval/merge, blocker resolution, and architecture/trade-off review aligned with Jira outcomes.
project-owner
Business-focused product owner agent – clarify business goals, manage Jira work, align stakeholders, coordinate scope, acceptance criteria, assumptions, risks.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.