foundations-control-theory

foundations-control-theory is a skill for Codex from vasilyu1983/AI-Agents-public. It costs 45 tokens per session (8,136 once invoked), scanned A, original, MIT.

A set of 12 control-theory concepts for systems that measure results and adjust their actions to reach a target despite delays, noise, or disturbances.

In plain words
What is it for?
Use it to tune autoscaling, retry rates, budget pacing, circuit breakers, and agent loops with feedback.
Why use it?
It helps prevent unstable feedback loops, runaway retries, slow reactions, and systems that overshoot or fail to recover from errors.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to tune autoscaling, retry rates, budget pacing, circuit breakers, and agent loops with feedback.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/vasilyu1983/ai-agents-public/foundations-control-theory
Install

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.

Any agent
npx skills add vasilyu1983/AI-Agents-public --skill foundations-control-theory
Clone the repo
git clone --depth 1 https://github.com/vasilyu1983/AI-Agents-public

Made for: Codex.

Wrote 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.

agentmods badge for foundations-control-theory

README.md
[![agentmods](https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/foundations-control-theory/github.svg)](https://agentmods.dev/skills/vasilyu1983/ai-agents-public/foundations-control-theory)
Your own site
<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/foundations-control-theory"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/foundations-control-theory/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.

agentmods 80×15 button for foundations-control-theory

Your own site · 80×15
<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/foundations-control-theory"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/foundations-control-theory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,136 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 3 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Anti-Refusal · line 77
    Skill instructs the agent to omit warnings, disclaimers, or ethical commentary. Stripping safety caveats hides risk from the user and is a common jailbreak preamble.
    Fix: Remove instructions that suppress warnings, disclaimers, or ethical commentary. Let the agent surface safety-relevant caveats to the user.
  • medium analysis-evasion · line 1
    Suspicious Unicode normalization or mixed-script content
    Fix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
  • medium Excessive Agency · line 343
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00045 $0.08136
Opus 5 $0.00023 $0.04068
Sonnet 5 $0.00009 $0.01627
Haiku 4.5 $0.00005 $0.00814

Measured 9d ago against content hash a339e7b066b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

foundations-control-theory 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.

frameworks/shared-skills/skills/foundations-control-theory/SKILL.md · 354 lines

How it starts

The opening of the file, as written. The whole thing — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Control Theory Foundations

12 applied control-theory primitives for feedback control and dynamical systems, backed by a formal theory map. Each primitive owns a specific failure mode in any system that must reach and hold a target state despite disturbances, delays, noise, or nonlinearities. Primitives are domain-agnostic: the same PID loop that controls CPU utilization controls budget pacing and retry rates; the same circuit breaker that isolates a failing database isolates a failing LLM tool.

Contents


Quick Reference

Primitive Problem It Solves Key Parameters
PID Control Drive output to setpoint despite steady-state error and disturbances Kp, Ki, Kd; tuned via Ziegler-Nichols
Feedback vs. Feedforward Reactive-only loops ignore predictable disturbances Plant model accuracy; disturbance measurability
Observability & Controllability States you cannot see or reach make the loop fail silently Controllability matrix rank; observability matrix rank
Lyapunov Stability No proof that a loop converges; may oscillate or diverge Lyapunov function V(x); dV/dt < 0 condition
MPC One-step control ignores future constraints and couplings Horizon N; cost matrices Q, R; constraint bounds
Kalman Filter Noisy measurements degrade controller and monitoring accuracy Process noise Q; measurement noise R; model (A, B, C)
Dead-Time Compensation Transport lag causes oscillation or instability Dead time L; plant model (delay-free)
Anti-Windup Integrator saturates during limit-clamping → overshoot on release Actuator min/max; tracking constant T_t
Gain Scheduling Single fixed-gain controller fails across operating regimes Scheduling variable σ; per-regime gain tables
Circuit Breaker & Backpressure Cascading failure; unbounded queue growth Failure threshold; timeout; half-open probe logic
Rate Limiting / Token Bucket Bursts and retry storms overload downstream; 429s cascade Fill rate r; burst capacity b; per-request cost s
DeePC / Behavioral Systems MPC without a plant model — unknown dynamics make model-based prediction impossible Hankel matrix T (data length); regularization λ_g, λ_y; persistency-of-excitation order

Read the full file on GitHub · 354 lines

Changes

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.

  1. 9d ago First seen · 354 lines · 45 tokens per session scan A a339e7b066b8

Subscribe to this mod's changes

foundations-control-theory is a skill published in the GitHub repository vasilyu1983/AI-Agents-public (87 stars, last pushed 10d ago), licensed MIT. It adds 45 tokens to every session and 8,136 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-09-03.

Related

Other skills, from other repositories

debugging-strategies

Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.

wshobson/agents · 43 tokens

git-advanced-workflows

Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.

wshobson/agents · 54 tokens

sql-optimization-patterns

Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database schemas, or optimizing application performance.

wshobson/agents · 44 tokens

parallel-debugging

Debug complex issues using competing hypotheses with parallel investigation, evidence collection, and root cause arbitration. Use this skill when debugging bugs with multiple potential causes, performing root cause analysis, or organizing parallel investigation workflows.

wshobson/agents · 44 tokens

error-handling-patterns

Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications. Use when implementing error handling, designing APIs, or improving application reliability.

wshobson/agents · 43 tokens

spark-optimization

Optimize Apache Spark jobs with partitioning, caching, shuffle optimization, and memory tuning. Use when improving Spark performance, debugging slow jobs, or scaling data processing pipelines.

wshobson/agents · 37 tokens