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 skills add atretyak1985/swarmery --skill summary-templatesgit clone --depth 1 https://github.com/atretyak1985/swarmeryWrote 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/skills/atretyak1985/swarmery/summary-templates)<a href="https://agentmods.dev/skills/atretyak1985/swarmery/summary-templates"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/summary-templates/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/skills/atretyak1985/swarmery/summary-templates"><img src="https://agentmods.dev/badge/skills/atretyak1985/swarmery/summary-templates.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.00059 | $0.00821 |
| Opus 5.5 | $0.00024 | $0.00328 |
| Sonnet 5.5 | $0.00012 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
summary-templates 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 1mo 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Provide standardized templates for structured summaries of technical work across four work types — task, feature, bug fix, refactoring — each with quantified metrics, role-specific instructions, and actionable next steps. This skill formats data you supply; it measures nothing and never modifies source files. The canonical end-of-task SUMMARY.md (seven fixed sections at the task root) belongs to session-closeout — defer to it for workspace task closeout; this skill keeps the per-change-type templates.
Rules (never violate)
- Never invent metrics — missing data is
N/A -- measure post-deploy, never a fabricated number. - Never include sensitive data (credentials, API keys, PII).
- Fill every template section or mark it
N/A; never silently omit one. - Produce summary documents only — never modify source files.
- Stay within the length budget: 200 lines markdown, 300 lines HTML.
- Document the template-selection reasoning, especially for ambiguous work types.
Resources
- Read
resources/template-structures.mdwhen selecting or filling a template: the four structures,.claude/templates/references and fallback rule, HTML mapping, domain-terminology guidance, worked examples. - Read
resources/authoring-procedure.mdwhen producing the summary: the 6-step procedure with checkpoints, self-check, mistakes, escalation, failure modes.
How to use
What it does
Turns finished work into a structured summary someone else can act on: one of four templates — task, feature, bug fix, refactoring — picked by the work's primary intent, filled with your real numbers, role-specific notes, and next steps that name an owner. Missing data is marked N/A, never guessed.
When to use it
- Someone asks to summarize a task, write a feature summary, or document what changed.
- A feature, bug fix, or refactoring needs a per-change-type completion report; an agent finished implementation and needs a structured write-up.
Not for: API documentation, changelogs, release notes, outage postmortems (troubleshooting), workspace task closeout (session-closeout), or measuring metrics.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 66 lines · 59 tokens per session scan A 2c536d45fb1f
summary-templates is a skill published in the GitHub repository atretyak1985/swarmery (7 stars, last pushed today), licensed Apache-2.0. It adds 59 tokens to every session and 821 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
execute
Execute phase — wave-based crew dispatch with critic gates and evidence-based verification.
recipe-batch-invite-to-event
Add a list of attendees to an existing Google Calendar event and send notifications.
recipe-block-focus-time
Create recurring focus time blocks on Google Calendar to protect deep work hours.
recipe-create-shared-drive
Create a Google Shared Drive and add members with appropriate roles.
recipe-find-free-time
Query Google Calendar free/busy status for multiple users to find a meeting slot.
recipe-organize-drive-folder
Create a Google Drive folder structure and move files into the right locations.