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 agentmods add skills/voxtechnologies/anty-framework/critical-chainnpx skills add VoxTechnologies/anty-framework --skill critical-chaingit clone --depth 1 https://github.com/VoxTechnologies/anty-frameworkWrote 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/voxtechnologies/anty-framework/critical-chain)<a href="https://agentmods.dev/skills/voxtechnologies/anty-framework/critical-chain"><img src="https://agentmods.dev/badge/skills/voxtechnologies/anty-framework/critical-chain.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.00053 | $0.01076 |
| Opus 5 | $0.00026 | $0.00538 |
| Sonnet 5 | $0.00011 | $0.00215 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
critical-chain 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- critical-chain — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Critical Chain & Buffer Management
When to Apply
- Managing Goal execution pace and timeline
- Buffer zone changes (GREEN/YELLOW/RED)
- Detecting and resolving bottlenecks
- Prioritizing which Actions to execute next
- When the founder asks "are we on track?"
Core Framework
TOC 5 Focusing Steps
Applied to the KPI tree. The Crux Driver (highest importance x tractability) is the constraint:
- IDENTIFY: The Crux Driver is the constraint — most important AND most solvable bottleneck
- EXPLOIT: Maximize that Driver's throughput. Execute its Actions first, eliminate waste, remove blockers. Never let constraint Actions wait.
- SUBORDINATE: All other Drivers serve the constraint. Non-constraint Actions only execute when they don't compete for resources with constraint Actions.
- ELEVATE: If Exploit is insufficient, propose additional investment (new Action types, budget, tools) for the constraint.
- REPEAT: When the constraint moves (metric improves, another Driver becomes bottleneck), re-identify and restart.
Buffer Management (3-Zone Traffic Light)
Buffer sizing: Project Buffer = 50% of estimated time to achieve Goal.
Feeding buffers: Each non-constraint Driver has a small feeding buffer protecting the constraint. If a non-constraint Action delays, the feeding buffer absorbs it.
| Zone | Buffer Consumed | Agent Behavior |
|---|---|---|
| GREEN (0-33%) | On track | Normal execution. Continue planned Actions. Light monitoring. |
| YELLOW (33-67%) | Falling behind | Investigate root cause. Generate recovery Actions. Notify user. Increase scan frequency. |
| RED (67-100%) | Significantly behind | Auto-propose high-impact recovery. Escalate to user. Deprioritize low-impact Drivers. Consider scope adjustment. |
Buffer consumed: 45% [========----------]
Goal progress: 34% [======------------]
Status: YELLOW — buffer consumption outpacing progress
Buffer as early warning: Unlike milestone tracking (detects problems after deadline miss), buffer management provides continuous visibility. YELLOW at 20% progress gives weeks of lead time.
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 · 87 lines · 53 tokens per session scan A 2313848922a8
critical-chain is a skill published in the GitHub repository VoxTechnologies/anty-framework (6 stars, last pushed 5mo ago), licensed MIT. It adds 53 tokens to every session and 1,076 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
pipeline
Cash Machine 10-step B2B sales pipeline with 3 presets, verifiable checkpoints per step, trajectory logging, bottleneck detection with utilization formula, lead qualification gate (BANT 6-criteria), pipeline velocity and stall detection (2x threshold), two-tier probability scoring, BBS tracking, end-of-quarter…
critical-chain
Theory of Constraints 5 Focusing Steps, buffer management with 3-zone traffic light, relay runner execution discipline, WIP limits, and late start scheduling. Use when managing Goal execution pace, detecting bottlenecks, or when buffer status changes.
choice-architecture
Nudge-based choice architecture for 3-option selection UI — smart default vs active choice, outcome mapping, channel factors, RECAP, operational transparency with source attribution, post-decision reinforcement, error-forgiving undo, peak-end session design, user contribution acknowledgment. Use when presenting…
quest-interview
QUEST Socratic interview methodology — beginner stance, empathic neutrality, downward/upward questioning, echo questions, concept identification, permission checks, critical point pursuit, anti-pattern safeguards, resolution imbalance diagnostic, workaround discovery, painkiller vs vitamin test, locally famous test.…
review-engine
5-question review framework (result, execution, plan, strategy, analysis), KPI propagation monitoring with 4-layer anomaly patterns, One-Way/Two-Way Door classification, withdrawal decision protocol, and assumption provenance auditing. Use during periodic reviews, buffer zone changes, or when evaluating why results…
anticipatory-selling
Auto-generate 5 sales support materials for pipeline Steps 5-7 — competitive comparison table, 3-year TCO analysis, internal proposal template, objection rebuttals, phased implementation timeline. Core principle is arming the buyer to sell internally. Use when deals reach Step 5+ or when win rates at Steps 5-7 are low.