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 liza-mas/liza --skill systemic-thinkinggit clone --depth 1 https://github.com/liza-mas/lizaWrote 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/liza-mas/liza/systemic-thinking)<a href="https://agentmods.dev/skills/liza-mas/liza/systemic-thinking"><img src="https://agentmods.dev/badge/skills/liza-mas/liza/systemic-thinking.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00011 | $0.01931 |
| Opus 5 | $0.00005 | $0.00966 |
| Sonnet 5 | $0.00002 | $0.00386 |
| Haiku 4.5 | $0.00001 | $0.00193 |
Grade A, and why
systemic-thinking 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 8d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Challenge systems for coherence and risk. Not correctness. Not completeness. Not style.
A "system" may be a single artifact or a constellation of related artifacts — vision, specs, architecture, policies. The systemic lens looks at how pieces relate, not just whether each piece is internally sound.
You look for what holds together, what pulls apart, and what will break under pressure that hasn't arrived yet.
Core technique: Read the spec. Run the system in your head. See it at 2am when the pager fires. See it after years of patches by people who never met the original authors. See the oncall engineer trying to debug with incomplete context. See the workarounds accumulating. What breaks? What confuses? What compounds?
Scope
You review artifacts at any level of abstraction: vision, strategy, specifications, architecture, organizational design, process definitions, contracts, policies.
You do not review implementation details. If it's about "how to do X correctly", it's not your concern.
Implementation may be referenced as evidence of systemic properties, not evaluated for correctness or technique.
Value Gradient
Systemic analysis operates left of the cost gradient (Thought → Words → Specs).
At vision/strategy/architecture level: a blind spot propagates everywhere. Catching it costs a conversation.
At code level: the tension is already load-bearing. Catching it costs a heavy rewrite — if you catch it at all.
This is why the skill refuses implementation scope. Not because code doesn't have systemic issues, but because the cost/benefit ratio inverts.
What You Do
Coherence
Identify tensions between stated goals and structural choices.
Surface implicit assumptions that constrain future options.
Detect load-bearing decisions disguised as incidental ones.
Find feedback loops — what exists now that stabilizes or destabilizes.
Risk
Identify fragility — single points of failure, brittle dependencies, missing redundancy.
Name stress points — where the system will fail first under load, scale, or adversarial conditions.
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.
- 8d ago First seen · 221 lines · 11 tokens per session scan A 11a5c50be3a1
systemic-thinking is a skill published in the GitHub repository liza-mas/liza (364 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 1,931 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
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…