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 byronxlg/skillfold --skill summarizationgit clone --depth 1 https://github.com/byronxlg/skillfoldWrote 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/byronxlg/skillfold/summarization)<a href="https://agentmods.dev/skills/byronxlg/skillfold/summarization"><img src="https://agentmods.dev/badge/skills/byronxlg/skillfold/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.
<a href="https://agentmods.dev/skills/byronxlg/skillfold/summarization"><img src="https://agentmods.dev/badge/skills/byronxlg/skillfold/summarization.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.00014 | $0.00362 |
| Opus 5.5 | $0.00006 | $0.00145 |
| Sonnet 5.5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
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.
What it actually says
Summarization
You condense information into clear, accurate summaries. You preserve what matters and cut what does not, adjusting detail level to the audience and purpose.
Principles
- A summary must be accurate - never introduce claims that are not in the source material
- Preserve the key points, conclusions, and actionable items
- Cut supporting detail, repetition, and tangential information
- Adjust length and detail to the audience: executives need conclusions, practitioners need specifics
- Maintain the original tone and intent - do not editorialize
Approach
When summarizing:
- Read the full source material before starting - understand the whole picture first
- Identify the main points: What are the key facts, decisions, or conclusions?
- Identify what is actionable: Are there tasks, deadlines, or decisions that require follow-up?
- Draft the summary at the requested detail level
- Verify that every claim in the summary is supported by the source material
- Check that no critical information was lost - would someone acting on this summary make the same decisions as someone who read the full text?
Detail Levels
- One-line: The single most important takeaway
- Brief (1-3 sentences): Key conclusion plus the most important supporting point
- Standard (1-2 paragraphs): All major points with enough context to understand them
- Detailed: All significant points with supporting evidence, organized by topic
Output
Produce a summary at the requested detail level. Lead with the most important information. Use structure (bullets, sections) when it improves scanability. If the source material contains action items or decisions, highlight them separately.
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.
- 2mo ago First seen · 39 lines · 14 tokens per session scan A 1d8d885ba68f
summarization is a skill published in the GitHub repository byronxlg/skillfold (15 stars, last pushed 6d ago), licensed MIT. It adds 14 tokens to every session and 362 once invoked, about $0.0001 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
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
typescript
Apply when writing TypeScript code. Strict types, discriminated unions, async patterns, and runtime safety.
writing-great-skills
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable. Read it before writing or changing a skill.
solid-generic
Use when building CLI tools, libraries, scripts, hooks, or non-framework TypeScript code (Bun/Node.js -- SOLID, files within FUSESOLIDMAXLINES, JSDoc mandatory).
mcp-server-patterns
Build MCP servers with Node/TypeScript SDK — tools, resources, prompts, Zod validation, stdio vs Streamable HTTP. Use Context7 or official MCP docs for latest API.
generating-typescript-types-from-apis
Generates TypeScript interfaces from API responses or OpenAPI schemas. Use when the user asks about typing API responses, creating interfaces from JSON, parsing Swagger/OpenAPI, or keeping types in sync with backend.