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 ysskrishna/ai-agent-skills --skill systems-thinkinggit clone --depth 1 https://github.com/ysskrishna/ai-agent-skillsWrote 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/ysskrishna/ai-agent-skills/systems-thinking)<a href="https://agentmods.dev/skills/ysskrishna/ai-agent-skills/systems-thinking"><img src="https://agentmods.dev/badge/skills/ysskrishna/ai-agent-skills/systems-thinking/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/ysskrishna/ai-agent-skills/systems-thinking"><img src="https://agentmods.dev/badge/skills/ysskrishna/ai-agent-skills/systems-thinking.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.00125 | $0.00805 |
| Opus 5 | $0.00063 | $0.00402 |
| Sonnet 5 | $0.00025 | $0.00161 |
| Haiku 4.5 | $0.00013 | $0.00081 |
Grade A, and why
systems-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 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systems Thinking
See the whole before optimizing parts. End with leverage-aware recommendations.
How to run it with this skill: one clearly headed section per phase in this order: Boundary → Structure → Dynamics → Delays → Leverage → Synthesis. Do not skip Structure before Leverage.
Setup (run before starting)
In one short block:
- System in focus — what is inside the boundary?
- Default pass — Boundary → Structure → Dynamics → Delays → Leverage → Synthesis (state this line)
If the boundary is unclear, ask at most 3 scoping questions in one message, then proceed. Note any remaining gaps or working guesses in plain language (no bracket tags in Setup).
If the user already named a proposed intervention, you may spend less text on Boundary but still must not skip Structure before Leverage.
The Phases
Boundary
What is in vs out of the system for this analysis? State the purpose of the system from a stakeholder view (one sentence).
Structure
Elements (stocks: things that accumulate; actors; resources) and flows (rates in/out). Use short bullet pairs: From → To with what moves.
Dynamics
Identify at least one reinforcing (R) and one balancing (B) loop if plausible. Format:
Loop [R|B]: … — Mechanism: …
If a loop does not apply, say so in one line and justify.
Delays
Where is time lag between action and effect? How does delay change behavior (overshoot, oscillation, learned helplessness)?
Leverage
Leverage point: … — Why it matters: … — Risk of backfire: …
Prefer interventions that change rules, information flows, or goals over name-and-shame unless evidence supports it; favor levers that shift incentives rather than only blaming individuals.
Synthesis
- System story — one paragraph in plain language (no jargon wall)
- Non-obvious consequence — at least one
- Recommended moves — 2–3 actions compatible with the map (not contradicted by delays/loops)
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 · 93 lines · 125 tokens per session scan A 9050edccfe77
systems-thinking is a skill published in the GitHub repository ysskrishna/ai-agent-skills (8 stars, last pushed 3mo ago), licensed MIT. It adds 125 tokens to every session and 805 once invoked, about $0.0006 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
dev-tools-skills-guide
Guide for development and code tools skills including document processing, browser automation, testing frameworks, and IDE integrations.
marketing-skills-guide
Guide for marketing and growth skills including SEO, copywriting, CRO, email campaigns, paid ads, and product launch strategies.
ai-llm-skills-guide
Guide for AI Agents and LLM development skills including RAG, multi-agent systems, prompt engineering, memory systems, and context engineering.
awesome-skills-overview
Guide for understanding and contributing to the awesome-skills curated resource list. Use this skill when adding resources, organizing categories, or maintaining README.md consistency (no duplicates).
agent-platforms
Guide for multi-platform skill compatibility across Claude Code, Codex, Gemini CLI, Cursor, GitHub Copilot, and other AI coding agents.
security-skills-guide
Guide for security-related Agent Skills including penetration testing, code auditing, threat hunting, and forensics skills.