Compute LadderSAFE
A framework-agnostic, git-native standard for defining AI agents
Overview
A framework-agnostic, git-native standard for defining AI agents
799d6d0ad18cOBSERVED · 2026-10-07What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
---
name: compute-ladder
version: 1.0.0
description: >
Model selection by provider health, not task complexity.
Tier 0 (local) handles most tasks. Paid models are break-glass only.
Fallbacks activate on 429 or timeout — never on perceived task difficulty.
---
# Compute Ladder
## Tier Definitions
```
Tier 0 — Local (never dies, zero cost)
ollama/qwen3-coder:latest primary, MoE, 128 TPS, 64k ctx
ollama/gpt-oss:20b fallback, 32k ctx HARD LIMIT
Tier 1 — Fast Free Cloud (up to 2100 TPS)
cerebras/qwen-3-235b-a22b-instruct-2507 235B MoE, fast free
cerebras/llama3.1-8b 8B, ultra-fast light tasks
Tier 2 — Free Cloud (normal latency)
openrouter/z-ai/glm-4.5-air
openrouter/qwen/qwen3-coder
Tier 3 — Free Cloud Deep Reasoning
openrouter/nousresearch/hermes-3-llama-3.1-405b:free
Tier 4 — Break-Glass (paid, restricted use)
openrouter/anthropic/claude-opus-4.6 [narco-check and audit ONLY]
```
## Fallback Rules
**DO fallback when:**
- HTTP 429 (rate limited)
- Connection timeout (> 90s)
- Stream death / incomplete response
**DO NOT fallback when:**
- Task seems "complex" or "important"
- You want "better" output quality
- Previous attempt gave a poor answer
Use the primary model. Iterate. Fallback is for infrastructure failure, not preference.
## Health Check
```bash
# Tier 0
curl -s localhost:11434/api/tags | python3 -c "import json,sys; d=json.load(sys.stdin); print('TIER-0 OK:', len(d['models']), 'models')"
# Tier 1
curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $CEREBRAS_API_KEY" \
https://api.cerebras.ai/v1/models
# Tier 4
curl -s -o /dev/null -w "%{http_code}" \
https://openrouter.ai/api/v1/models
```
## Cost Guard
```bash
# Check today's OpenRouter spend
curl -s "https://openrouter.ai/api/v1/auth/key" \
-H "Authorization: Bearer $OPENROUTER_API_KEY" \
| python3 -c "
import json,sys
d=json.load(sys.stdin)['data']
print(f'today: \${d[\"usage_daily\"]:.2f} | week: \${d[\"usage_weekly\"]:.2f} | month: \${d[\"usage_monthly\"]:.2f}')
"
```
Daily > $5: flag to Ludo.
Weekly > $50: flag immediately — tier-4 model is likely being over-used.Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
799d6d0ad18cfull audit observations/trust-audit/skill/open-gitagent__compute-ladder.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | 799d6d0ad18c | SAFE | B | 89 | first audit |
Questions
What does the Compute Ladder skill do?
A framework-agnostic, git-native standard for defining AI agents
Is Compute Ladder safe to install?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.
What can Compute Ladder access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (799d6d0ad18c), read on 2026-10-07. The repository is watched, and a new audit runs when it changes — this is the first audit.