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/clawdotnet/openclaw.net/summarizenpx skills add clawdotnet/openclaw.net --skill summarizegit clone --depth 1 https://github.com/clawdotnet/openclaw.netWhat 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.00025 | $0.00292 |
| Opus 5 | $0.00013 | $0.00146 |
| Sonnet 5 | $0.00005 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
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.
What it actually says
Summarize
When the user asks to summarize, condense, or get a digest of content, produce a structured summary.
Format
- Key Points — 3–5 bullet points of the most important information
- Details — Brief expansion on each key point if the user needs more depth
- Action Items — Any tasks, decisions, or follow-ups identified (omit if none)
Guidelines
- Keep summaries concise. Default to 3–5 key points unless the user asks for more.
- Prioritize what matters to the user's stated goal. If the goal is unclear, ask before summarizing.
- Preserve factual accuracy. Do not invent dates, names, numbers, or conclusions not present in the source.
- When summarizing a conversation or thread, distinguish between facts, opinions, decisions, and open questions.
- For long content, consider a two-pass approach: first extract the structure (sections, topics), then summarize each with appropriate depth.
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 · 30 lines · 25 tokens per session scan A 6116800aaf8b
summarize is a skill published in the GitHub repository clawdotnet/openclaw.net (487 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 292 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-30.
Other skills, from other repositories
video2knowledge
Convert videos into timestamped subtitles and structured knowledge artifacts. Two ingestion paths: (1) a native multimodal VLM (at most 4B params, via Ollama) reads sampled video frames into timestamped captions; (2) faster-whisper ASR transcribes the audio into timestamped subtitles. Then refine into a structured…
image-understanding
Enable image understanding capabilities for describing/analyzing images, reading text, and answering questions about visual content.
superplane-changelog
When generating a SuperPlane changelog from merged commits. Use for "what's new" summaries with new integrations, new components/triggers, improvements, security updates, and bug fixes. Output is user-focused markdown in tmp/.
review-agents-md
Audit Dograh AGENTS.md files for drift against the live repo and for bad scope boundaries between parent and child docs. Use when the user asks to review existing AGENTS files, identify stale guidance, decide whether a subtree needs its own AGENTS.md, or update the AGENTS.md hierarchy under the repo root, api/, or ui/.
datadesigner-docs
Maintain the NeMo Data Designer Fern docs site under fern/. Use for any documentation change. Triggered by: "edit docs", "add doc page", "update docs", "rename page", "fix broken link", "add redirect", "preview docs", "publish docs", "regenerate notebooks", "update dev note", any request that touches fern/.
commit
Commit current changes with a clear, descriptive message.