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 OneDro1d/dark-factory --skill vinculum-loopgit clone --depth 1 https://github.com/OneDro1d/dark-factoryWrote 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/onedro1d/dark-factory/vinculum-loop)<a href="https://agentmods.dev/skills/onedro1d/dark-factory/vinculum-loop"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/vinculum-loop.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.00138 | $0.01895 |
| Opus 5 | $0.00069 | $0.00948 |
| Sonnet 5 | $0.00028 | $0.00379 |
| Haiku 4.5 | $0.00014 | $0.00189 |
Grade A, and why
vinculum-loop 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 4d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vinculum Loop — the autonomous, governed dev loop for any project
Two pieces work together. Keep them distinct:
- The loop = orchestration. The
dark-factory-buildskill + the Workflow tool. This is what actually runs: mission → discover → PO → design → TDD build → deploy → test → ship — autonomously, sub-agent-fanned, Promise-Theory-verified. Works on any project today. - The substrate = trust / provenance (optional, not in this package). A separate, harness/LLM-agnostic signed-provenance layer can record every decision/action as a hash-chained, append-only ledger entry. It is not bundled here and not required — the loop runs fully without it. Enable it later only if your org wants cryptographic provenance.
You run the loop with
dark-factory-build. The signed-provenance substrate is an optional layer underneath — the loop's correctness rests on Promise-Theory verification, not on signing.
When to use
- "Give me a mission objective and full autonomy" → the 2-trigger contract.
- "Run the loop / vinculum loop on
<project>." - Any non-trivial build you want done end-to-end: evidence-gated, ticketed, documented.
The contract the loop guarantees (the VR invariants)
- VR-5 — 2-trigger notify: come back only when the objective is met or blocked on all fronts. No step-wise check-ins.
- A/B/C decisions: A = hard blocker → escalate · B = reversible → decide + log · C = "is it done?" → own the judgment.
- VR-1 — evidence-gated (Promise Theory): decisions rest on proven claims; a sub-agent's "done / all passing" is unverified until you re-run its evidence.
- VR-3 — sensitive data never cleartext public: keep PHI/secrets private; publish only hashes/metadata.
- VR-7 — harness/LLM-agnostic: Claude Code or any agentic harness; API key, subscription, or local OS model.
- VR-2 / VR-6 — sign-before-act + append-only hash-chained ledger: provided by the optional provenance substrate. Not active in the default unsigned mode described here.
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.
- 4d ago Changed · +28 lines a925a6037474
- 7d ago First seen · 58 lines · 138 tokens per session scan A 0c731d770251
vinculum-loop is a skill published in the GitHub repository OneDro1d/dark-factory (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 138 tokens to every session and 1,895 once invoked, about $0.0007 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-01.
Other skills, from other repositories
engram-testing-coverage
TDD and coverage standards for Engram. Trigger: When implementing behavior changes in any package.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
tdd
This skill should be used when the user wants to implement features or fix bugs using test-driven development. Enforces the RED-GREEN-REFACTOR cycle with vertical slicing, context isolation between test writing and implementation, human checkpoints, and auto-test feedback loops. Uses multi-agent orchestration with the…
conductor-implement
Execute tasks from a track's implementation plan following TDD workflow.
mobiai-mobile-tdd
You MUST use this before writing any implementation code for a mobile feature, bug fix, refactor, or behavior change. Tests come before implementation — no exceptions.