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 rossoctl/examples --skill summarizergit clone --depth 1 https://github.com/rossoctl/examplesWrote 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/rossoctl/examples/summarizer)<a href="https://agentmods.dev/skills/rossoctl/examples/summarizer"><img src="https://agentmods.dev/badge/skills/rossoctl/examples/summarizer/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/rossoctl/examples/summarizer"><img src="https://agentmods.dev/badge/skills/rossoctl/examples/summarizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00071 | $0.02197 |
| Opus 5.5 | $0.00028 | $0.00879 |
| Sonnet 5.5 | $0.00014 | $0.00439 |
| Haiku 4.5 | $0.00007 | $0.00220 |
Grade A, and why
summarizer 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 — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Information Summarization Skill
Overview
This skill helps you create crisp, clear, and effective summaries of any type of information. Whether you're dealing with lengthy documents, technical content, meeting notes, or research papers, this skill provides structured approaches and tools to extract and present the most important information concisely.
Core Principles
1. Clarity First
- Use simple, direct language
- Avoid jargon unless necessary
- Define technical terms when used
- Write for your target audience
2. Conciseness
- Remove redundant information
- Focus on key points only
- Use active voice
- Eliminate filler words
3. Structure
- Start with the most important information
- Use hierarchical organization
- Group related concepts
- Maintain logical flow
4. Completeness
- Capture all essential points
- Preserve critical context
- Include relevant data/numbers
- Maintain accuracy
Summarization Techniques
Extractive Summarization
Select and extract the most important sentences or phrases directly from the source:
When to use:
- Technical documentation
- Legal documents
- Scientific papers
- When exact wording matters
Approach:
- Identify topic sentences
- Extract key facts and figures
- Select representative quotes
- Maintain original phrasing
Abstractive Summarization
Rewrite and rephrase content in your own words:
When to use:
- General articles
- Meeting notes
- Narrative content
- When clarity is more important than exact wording
Approach:
- Understand the core message
- Identify main themes
- Rephrase in simpler terms
- Create new sentences that capture essence
Hybrid Approach
Combine both techniques for optimal results:
- Extract key facts and data (extractive)
- Rephrase explanations (abstractive)
- Organize logically
- Add context where needed
Summary Formats
Executive Summary
Length: 10% of original or 1-2 paragraphs Structure:
- Opening statement (main point)
- Key findings (2-4 bullets)
- Conclusion/recommendation
What ships with it
5 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 · 364 lines · 71 tokens per session scan A 8dc9f3b65a59
summarizer is a skill published in the GitHub repository rossoctl/examples (11 stars, last pushed yesterday), licensed Apache-2.0. It adds 71 tokens to every session and 2,197 once invoked, about $0.0003 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-30.
Other skills, from other repositories
importing-a-codebase
Use when asked to create the initial spec graph for an existing codebase that has source code but no specs. Normally reached via setting-up-a-project.
starting-a-new-project
Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.
managing-mcp-servers
Use when the user asks to add, change, remove, enable or disable an MCP server, or when an MCP tool is missing, needs sign-in, fails, or was blocked. ThinkRail runs pi in-process, so there is no pi command to call.
todos
Use when the user asks for a shared plan, a task needs at least three substantive execution steps, or a loose TODO is pending. Without an explicit plan request, not for one-shot answers or checks, or one- to two-step work that is not already in the list.
asking-user-questions
Use when composing an askuserquestion round inside a workflow, or when a workflow skill names it at a question step. Shared norms for the tool — not a workflow, nothing to execute.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.