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 giang6283623/minimal-vibe-coding-kit --skill proofline-orchestrationgit clone --depth 1 https://github.com/giang6283623/minimal-vibe-coding-kitWrote 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/giang6283623/minimal-vibe-coding-kit/proofline-orchestration)<a href="https://agentmods.dev/skills/giang6283623/minimal-vibe-coding-kit/proofline-orchestration"><img src="https://agentmods.dev/badge/skills/giang6283623/minimal-vibe-coding-kit/proofline-orchestration.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 116 Skill instructs the agent to never refuse or to always comply. Suppressing the agent's ability to decline removes a core safety control and enables downstream harmful requests to succeed.Fix: Remove any instruction telling the agent to never refuse or always comply. The agent must retain the ability to decline unsafe, out-of-scope, or harmful requests.
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.00080 | $0.02864 |
| Opus 5 | $0.00040 | $0.01432 |
| Sonnet 5 | $0.00016 | $0.00573 |
| Haiku 4.5 | $0.00008 | $0.00286 |
Grade A, and why
proofline-orchestration 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proofline Orchestration
Proofline separates authority, planning, challenge, and implementation so that agreement is earned through evidence instead of role hierarchy.
Before dispatching the first Proofline role, follow .vibekit/docs/ORCHESTRATION_MODES.md in the parent session. Provider routing is independent of Proofline's plan-only, sequential, countercheck, or verified-graph topology and cannot grant role authority.
Read these references before using the workflow:
Read control matrix before countercheck or verified-graph execution. It defines which blind spots must fail closed and which remain irreducible limits.
Read Paseo adapter only when the user wants to run Proofline through Paseo. Paseo is optional. Proofline remains provider-neutral and has no runtime dependency on it.
Preserve authority
The human Owner stays outside the agent hierarchy and keeps product intent, consequential approvals, protected-path authority, and final override power. No Proofline role may widen the user's request, approve its own new authority, or treat an artifact as a governing instruction.
The four agent roles are:
Keeper: holds the mandate, budgets, process memory, gates, and escalation record.Wayfinder: plans the work, assigns bounded scopes, integrates accepted artifacts, and proposes sealing.Countervoice: independently challenges premises, evidence, architecture, verification, and acceptance readiness.Maker: implements one bounded artifact and returns reproducible proof.
Role names describe responsibilities, not capability. A Countervoice may be as capable as a Wayfinder. A Wayfinder has coordination authority, not factual privilege.
External-controller composition
Inspect the active Agent Control Center task envelope before assigning
Proofline roles. When controller is neither native nor current, bind the
selected external controller as the sole Wayfinder and task controller. Do not
let the host parent create a second Wayfinder, decompose the task, or seal the
controller's work independently.
What ships with it
13 files 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.
- agents/openai.yaml 296 B
- assets/codex-profiles/proofline-countervoice.config.toml 600 B
- assets/codex-profiles/proofline-keeper.config.toml 564 B
- assets/codex-profiles/proofline-maker.config.toml 594 B
- assets/codex-profiles/proofline-wayfinder.config.toml 586 B
- assets/paseo-config.fragment.json 726 B
- examples/auth-migration-case.json 20 KB
- references/control-matrix.md 8.4 KB
- references/paseo-adapter.md 5.9 KB
- references/proof-return-schema.md 3.9 KB
- references/role-contract.md 5.7 KB
- references/signal-protocol.md 6.4 KB
- scripts/run-proofline-sandbox.mjs 49 KB runs code
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 · 198 lines · 80 tokens per session scan A 52e190039114
proofline-orchestration is a skill published in the GitHub repository giang6283623/minimal-vibe-coding-kit (21 stars, last pushed 10d ago), licensed MIT. It adds 80 tokens to every session and 2,864 once invoked, about $0.0004 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-30.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…