agentmods.dev

summarization

summarization is a skill for Claude Code, Codex from flukeatzerocool/infobroker. It costs 50 tokens per session (580 once invoked), scanned A, original, MIT.

A method for condensing documents, articles, or other text while preserving their main points and important details.

In plain words
What is it for?
Use it to create short summaries, detailed breakdowns, paraphrases, or combined summaries of several documents.
Why use it?
It reduces the time needed to understand long or multiple sources without adding unsupported claims.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions OpenCode.

not rated 1repo +1 2d ago A scan 50 tokens original MIT

Good fit Use it to create short summaries, detailed breakdowns, paraphrases, or combined summaries of several documents.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/flukeatzerocool/infobroker/summarization
View source ↗ flukeatzerocool/infobroker
Install

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.

Any agent
npx skills add flukeatzerocool/infobroker --skill summarization
Clone the repo
git clone --depth 1 https://github.com/flukeatzerocool/infobroker

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for summarization

README.md
[![agentmods](https://agentmods.dev/badge/skills/flukeatzerocool/infobroker/summarization/github.svg)](https://agentmods.dev/skills/flukeatzerocool/infobroker/summarization)
Your own site
<a href="https://agentmods.dev/skills/flukeatzerocool/infobroker/summarization"><img src="https://agentmods.dev/badge/skills/flukeatzerocool/infobroker/summarization/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.

agentmods 80×15 button for summarization

Your own site · 80×15
<a href="https://agentmods.dev/skills/flukeatzerocool/infobroker/summarization"><img src="https://agentmods.dev/badge/skills/flukeatzerocool/infobroker/summarization.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 580 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.00580
Opus 5.5 $0.00020 $0.00232
Sonnet 5.5 $0.00010 $0.00116
Haiku 4.5 $0.00005 $0.00058

Measured 2mo ago against content hash c1a36560843e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

summarization 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 2mo 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.

skills/summarization/SKILL.md · 77 lines

How it starts

The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Summarization

When NOT to Use

  • When the source is already very short (under 100 words); offer to highlight key sentences instead.
  • When the user needs exact quotes rather than a paraphrase.

Workflow

  1. Analyze the input. Determine length, structure, domain, and whether it is one document or many.

  2. Choose the strategy.

    • Extractive: Keep key sentences verbatim for factual or legal texts.
    • Abstractive: Rewrite in new words for readability.
    • Hierarchical: Provide a one-line TLDR, a short paragraph, and a detailed breakdown.
    • Multi-document: Synthesize across several sources.

  3. Identify key information. Extract core claims, findings, decisions, action items, and supporting data. Rank by importance.

  4. Generate the summary. Match the requested length and detail. Preserve factual accuracy. Do not introduce information not in the source.

  5. Verify faithfulness. Compare the summary against the source. Check numbers, proper nouns, and causal claims.

Best Practices

  • Front-load the most important information.
  • Preserve numerical precision.
  • Match the source's tone.
  • For multi-document summaries, organize by theme rather than by source.
  • Flag contradictions rather than choosing one side.

Output Contract

Always end with a searchable one-line status:

summarization complete. <N> key points | source facts preserved: <pass/flag>

<pass/flag> is pass when the summary preserves the source's numbers, proper nouns, and causal claims, otherwise flag with the discrepancy noted.

Edge Cases

  • Contradictory source: Highlight the contradiction in the summary.
  • Technical jargon: Define terms for non-specialists; preserve vocabulary for experts.
  • Truncated source: Note that the summary may be incomplete.
  • Overlapping sources: Deduplicate repeated information.

Infobroker Integration

This skill is the condense step of the Infobroker Research & Write and Fact-Check pipelines. It condenses verified findings into a concise digest before technical-writing produces the final output.

Read the full file on GitHub · 77 lines

Changes

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.

  1. 2mo ago First seen · 77 lines · 50 tokens per session scan A c1a36560843e

Subscribe to this mod's changes

summarization is a skill published in the GitHub repository flukeatzerocool/infobroker (1 stars, last pushed 2d ago), licensed MIT. It adds 50 tokens to every session and 580 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-08-31.

Writing and docs
Related

summarization compared with skills from other repositories

summarization next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
summarizationflukeatzerocool/infobrokerSkill12d agoMITA50Claude Code, Codex
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code