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/cyrusagents/cyrus/summarizenpx skills add cyrusagents/cyrus --skill summarizegit clone --depth 1 https://github.com/cyrusagents/cyrusWrote 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/cyrusagents/cyrus/summarize)<a href="https://agentmods.dev/skills/cyrusagents/cyrus/summarize"><img src="https://agentmods.dev/badge/skills/cyrusagents/cyrus/summarize.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.00305 |
| Opus 5 | $0.00017 | $0.00152 |
| Sonnet 5 | $0.00007 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
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 4d 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
Format a final summary of the work completed. Your output will be automatically rendered inside Linear — just write it as your response. Do not use any tool to post or save it.
Content
Cover the following:
- Work Completed — What was accomplished (1-2 sentences) and key outcome
- Key Details — Files modified, important changes, PR link if created
- Status — Completion status and any follow-up needed
Format
- Aim for 3-5 paragraphs maximum
- Use clear, professional language suitable for Linear
- Use markdown formatting for readability
- Collapsible sections: Wrap "Changes Made" and "Files Modified" in
+++Section Name\n...\n+++ - @mentions: Use the Linear profile URL format from
<assignee>context (e.g.https://linear.app/<workspace>/profiles/<username>)
Example
## Summary
[Brief description of what was done]
+++Changes Made
- [Key change 1]
- [Key change 2]
+++
+++Files Modified
- [File 1]
- [File 2]
+++
## Status
[Current status and any next steps]
[PR link if applicable]
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.
- 4d ago First seen · 48 lines · 34 tokens per session scan A af82e3db586f
summarize is a skill published in the GitHub repository cyrusagents/cyrus (796 stars, last pushed today), licensed Apache-2.0. It adds 34 tokens to every session and 305 once invoked, about $0.0002 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
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.
bootstrap-repo-analysis
First-time analysis of a repository with no prior reviewer outcomes. Crawl historical merged-PR review feedback with the gh CLI (plus any preloaded samples), extract the team's review norms, and synthesize the initial per-repo review-style prompt. Use this for a cold-start repo; use continual-learning instead once the…
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
continual-learning
Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…
linearis
Manage Linear.app work from the command line with the linearis CLI (bins linearis / linear), which outputs JSON: issues/tickets, projects, cycles (sprints), milestones, initiatives (roadmap), documents, labels, teams, users, and issue discussions/comments. Use when the user mentions Linear, a ticket identifier like…
dotcraft-unity
Use when dotcraft-unity MCP or unityexecutecsharp is available, or when the user asks to inspect, automate, capture, or debug Unity Editor state, scenes, assets, Console logs, or GameView output. Provides background-first Unity Editor automation rules.