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 cdeust/zetetic-team-subagents --skill systems-leveragegit clone --depth 1 https://github.com/cdeust/zetetic-team-subagentsWrote 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/cdeust/zetetic-team-subagents/systems-leverage)<a href="https://agentmods.dev/skills/cdeust/zetetic-team-subagents/systems-leverage"><img src="https://agentmods.dev/badge/skills/cdeust/zetetic-team-subagents/systems-leverage.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.1 | $0.00063 | $0.00687 |
| Opus 5 | $0.00032 | $0.00344 |
| Sonnet 5 | $0.00013 | $0.00137 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
systems-leverage 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Systems Leverage
Problem shape: the system misbehaves as a whole while every part looks locally fine. Interventions at the parameter level keep failing because the structure — feedback loops, stocks, delays, governance rules — produces the behavior. The move: map the structure, rank the leverage points, intervene as high as is accessible.
Relevant geniuses
| Agent | Use when |
|---|---|
| meadows | many possible interventions, unclear where to focus; recurring archetype; confusing accumulation-and-delay behavior |
| beer | organization fails despite local fixes — audit the five viable-system functions; variety mismatch with the environment |
| kauffman | system too rigid or too chaotic — tune connectivity; explore the adjacent possible instead of leaping |
| deming | management reacts to noise; quality inspected in at the end instead of built into the process |
| ostrom | a shared resource (build pipeline, on-call, budget, commons) is being depleted — check the eight design principles, rules-in-use vs rules-on-paper |
| margulis | competing units would gain more by merging — symbiosis as an architectural option |
| rogers | a change/tool isn't being adopted — segment the adopters, diagnose the chasm, audit the innovation's attributes |
| schelling | macro pattern emerges from micro choices nobody intended — model the tipping points before moralizing the outcome |
Invocation
- Pick the best-fit agent above. If two or more fit, run
tools/genius-invoker.sh route "<problem>"and take the top ranked match. - Load it:
tools/genius-invoker.sh invoke <agent> "<problem>", then readagents/genius/<agent>.mdin full. - Apply the agent's
<workflow>step by step and answer in its<output-format>. Deliver the structural diagnosis (loop, stock, rule) before any parameter recommendation. - Typical chain: meadows maps and ranks leverage → beer audits the control
structure → rogers plans the adoption. Run via
tools/genius-invoker.sh compose meadows beer -- "<problem>". - If no shape above matches, use a standard team agent instead.
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 · 51 lines · 63 tokens per session scan A 80a9500fce3b
systems-leverage is a skill published in the GitHub repository cdeust/zetetic-team-subagents (7 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 687 once invoked, about $0.0003 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
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
review
5-pass structured code review — correctness, security, performance, readability, consistency.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.
extract-resume
Parse a resume's uploaded PDF into structured JSON (basics, experience, projects, skills, education) and save it to the editor.
codex-test-gen
Generate unit tests for specified functions using Codex exec.
ensure-pipelines-host
Ensures the tenant has a usable Power Platform Pipelines host environment before any pipeline operation runs. Detects host state via the same resolution order as the Power Apps UI (org-db setting → BAP env metadata → default-custom-host setting); if any existing host (Platform or Custom) is found, uses it. If no host…