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 OutlineDriven/odin-claude-plugin --skill automatic-cybernetic-flow-designgit clone --depth 1 https://github.com/OutlineDriven/odin-claude-pluginWrote 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/outlinedriven/odin-claude-plugin/automatic-cybernetic-flow-design)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/automatic-cybernetic-flow-design"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/automatic-cybernetic-flow-design/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/outlinedriven/odin-claude-plugin/automatic-cybernetic-flow-design"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/automatic-cybernetic-flow-design.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.00058 | $0.00910 |
| Opus 5 | $0.00029 | $0.00455 |
| Sonnet 5 | $0.00012 | $0.00182 |
| Haiku 4.5 | $0.00006 | $0.00091 |
Grade A, and why
automatic-cybernetic-flow-design 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 6d 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.
This is a copy
100% identical to automatic-cybernetic-flow-design — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automatic cybernetic flow design
Contract
| Field | Bound contract |
|---|---|
| Trigger | User wants a cybernetic flow design document specifying sensors, actuators, feedback paths, delays, and oscillation risk for an interactive system. |
| Authority | Write only the single named local design document; delete or overwrite that file to roll back. Do not implement, deploy, or mutate source code. |
| Side effect | A cybernetic flow design document at the named local path. No source code, runtime, or remote mutation. |
| Done | A design document with sections for sensors, actuators, feedback, delay, oscillation, a wiring diagram, and a dynamic-routing note, written to the named local file. |
Inputs
Required:
- The interactive system description: what state it controls, what it observes, and what actions it can take.
- The primary control objective: the state the system tries to hold or steer.
- Observable signals (sensors) and available actions (actuators).
- Per-path delay classifications: fixed, variable, or bounded with the bound.
- The named local output file path.
Optional:
- Known latency budgets, stability requirements, existing feedback paths, or constraints on sensors and actuators.
- Gain and timing data for oscillation analysis. If absent, the path is marked under-specified.
Procedure
-
Intake and validate the system description and control objective. Confirm the system is named, the control objective is stated, and the output file path is supplied. Done when: the system, control objective, and output file path are confirmed.
-
Enumerate sensors and actuators. For each sensor, name the quantity measured and its source. For each actuator, name the effect and its range. State the count of each. Done when: every sensor and actuator is listed with its quantity, source or effect, and range.
-
Map feedback paths. For each path, specify which sensor(s) drive which actuator(s), the comparison that generates the error signal, and the direction of correction. Allow many-to-one and coordinated relationships; a single sensor may drive multiple actuators and multiple sensors may converge on one actuator. Done when: every feedback path names its sensors, actuators, error comparison, and correction direction.
What ships with it
1 file 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.
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.
- 6d ago First seen · 54 lines · 58 tokens per session scan A e9a3a8224151
automatic-cybernetic-flow-design is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed yesterday), licensed Apache-2.0. It adds 58 tokens to every session and 910 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to automatic-cybernetic-flow-design, differing in 4 lines, and is treated as a copy.
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…