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 cyyeh/skills-playground --skill system-analyzergit clone --depth 1 https://github.com/cyyeh/skills-playgroundWrote 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/cyyeh/skills-playground/system-analyzer)<a href="https://agentmods.dev/skills/cyyeh/skills-playground/system-analyzer"><img src="https://agentmods.dev/badge/skills/cyyeh/skills-playground/system-analyzer/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/cyyeh/skills-playground/system-analyzer"><img src="https://agentmods.dev/badge/skills/cyyeh/skills-playground/system-analyzer.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.00133 | $0.04312 |
| Opus 5 | $0.00067 | $0.02156 |
| Sonnet 5 | $0.00027 | $0.00862 |
| Haiku 4.5 | $0.00013 | $0.00431 |
Grade A, and why
system-analyzer 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 9d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
System Analyzer
Perform deep-dive research on a selected software system and produce a structured analysis markdown file. The output is organized by depth levels (Beginner / Intermediate / Advanced) and designed to feed into the system-to-course skill for HTML course generation.
First-Run Welcome
When triggered, introduce yourself and explain what you do:
I can produce a comprehensive analysis of any software system — organized by depth levels so it works for beginners and experts alike.
Point me at a system:
- By name — e.g., "analyze Kafka", "deep dive into Redis"
- From a finder report — if you ran system-finder, I'll look for
finder-report.mdin the output directoryI'll research the system thoroughly — architecture, internals, trade-offs, real-world usage — and produce a structured
analysis.mdwith level tags (beginner, intermediate, advanced) that the course generator can consume directly.
Output Directory
Always ask the user where to save the analysis before writing any files. Use AskUserQuestion to prompt:
Where would you like me to save the analysis file? Default:
dist/[system-name]/
Accept the user's chosen path. If they accept the default or say something like "that's fine" or "default", use dist/[system-name]/. Store this path as [output-dir].
Exception: When called by the system-explorer orchestrator with a pre-determined output directory, use that directory without re-asking.
Create the directory if it does not exist.
Input
- From a prior system-finder run: Check for
[output-dir]/finder-report.md. If it exists, read it to get the system name, category, and any preliminary notes. Confirm the system with the user before proceeding. - Direct from user: Accept a system name (e.g., "Kafka", "SQLite", "Kubernetes"). Confirm before starting research.
Always confirm the system before starting. State what you understood and ask: "Ready to begin the deep dive?"
The Process (4 Phases)
What ships with it
12 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.
- references/analysis-template.md 12 KB
- references/section-templates/00-metadata.md 1.9 KB
- references/section-templates/01-overview.md 1.1 KB
- references/section-templates/02-core-concepts.md 1.3 KB
- references/section-templates/03-architecture.md 1.6 KB
- references/section-templates/04-how-it-works.md 1.4 KB
- references/section-templates/05-implementation-details.md 5.4 KB
- references/section-templates/06-use-cases.md 1.3 KB
- references/section-templates/07-ecosystem.md 1.2 KB
- references/section-templates/08-common-qa.md 1.4 KB
- references/section-templates/09-tradeoffs.md 1.5 KB
- references/section-templates/manifest-template.json 1.1 KB
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.
- 9d ago First seen · 240 lines · 133 tokens per session scan A 7742fabc762b
system-analyzer is a skill published in the GitHub repository cyyeh/skills-playground (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 133 tokens to every session and 4,312 once invoked, about $0.0007 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…