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 skills/pilotspace/pilot-space/summarizenpx skills add pilotspace/pilot-space --skill summarizegit clone --depth 1 https://github.com/pilotspace/pilot-spaceWhat 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.00019 | $0.01906 |
| Opus 5 | $0.00010 | $0.00953 |
| Sonnet 5 | $0.00004 | $0.00381 |
| Haiku 4.5 | $0.00002 | $0.00191 |
Grade A, and why
summarize 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 2d 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 — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize Skill
Generate summaries of notes, issues, PR discussions, or documentation in multiple formats.
Quick Start
Use this skill when:
- User requests summary (
/summarize) - Long note/issue needs TLDR
- PR review summary needed
Example:
Content: [Long discussion about authentication redesign - 500 words]
Summary (brief):
"Redesign auth to use JWT tokens instead of sessions. Requires DB schema
changes and API updates. Estimated 2 weeks. Security audit needed."
Summary (bullet):
- Replace session cookies with JWT tokens
- Update DB schema for refresh tokens
- Modify login/logout API endpoints
- Conduct security review before deployment
- Estimated: 2 weeks (1 backend + 1 testing)
Workflow
-
Analyze Content
- Identify content type (note, issue, PR, docs)
- Extract key points and decisions
- Detect action items and owners
- Find technical details and requirements
-
Choose Summary Format
- Bullet: Quick scan, action-oriented
- Brief: Single paragraph TLDR
- Detailed: Multi-paragraph with sections
- Executive: Business-focused, non-technical
-
Generate Summary
- Preserve critical information (dates, numbers, names)
- Maintain technical accuracy
- Highlight decisions and action items
- Include confidence tag if summarizing recommendations
-
Validate Completeness
- No information loss of critical facts
- Preserves author intent
- Maintains chronological order if relevant
Output Format
{
"format": "bullet",
"summary": "- Point 1\n- Point 2\n- Point 3",
"confidence": "RECOMMENDED",
"word_count": {
"original": 500,
"summary": 45,
"compression_ratio": 0.09
},
"key_points": [
{"type": "decision", "text": "Use JWT tokens"},
{"type": "action", "text": "Security audit needed", "owner": "security-team"},
{"type": "estimate", "text": "2 weeks development"}
],
"missing_info": [
"Timeline for security audit not specified",
"Rollback strategy not discussed"
]
}
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.
- 2d ago First seen · 197 lines · 19 tokens per session scan A 4d26aa9c6181
summarize is a skill published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 19 tokens to every session and 1,906 once invoked, about $0.0001 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.