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 Chisiki1/objective-integrity-framework --skill scenario-interaction-closuregit clone --depth 1 https://github.com/Chisiki1/objective-integrity-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/chisiki1/objective-integrity-framework/scenario-interaction-closure)<a href="https://agentmods.dev/skills/chisiki1/objective-integrity-framework/scenario-interaction-closure"><img src="https://agentmods.dev/badge/skills/chisiki1/objective-integrity-framework/scenario-interaction-closure/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/chisiki1/objective-integrity-framework/scenario-interaction-closure"><img src="https://agentmods.dev/badge/skills/chisiki1/objective-integrity-framework/scenario-interaction-closure.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.00035 | $0.00278 |
| Opus 5.5 | $0.00014 | $0.00111 |
| Sonnet 5.5 | $0.00007 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
scenario-interaction-closure 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 1mo 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.
What it actually says
Scenario interaction closure
Use for a material candidate edit, migration, or released action when normal success depends on state, owner, consumer, ordering, recovery, or cross-component evidence.
- Derive initial scenarios from the source-bound objective, normal-success envelope, state/owner/consumer/dependency boundaries and change/fault boundary. Do not seed initial generation with an observed error, patch, or test.
- Record factors, reachable edges/hyperedges, semantic locks, local and relational claims, final consumer oracles, unmasking/recovery, and a disposition for every frozen relation.
- Decompose only when the retained local and relational evidence has a recomposition witness. A missing relation is an orphan, not a PASS.
- Run
python -B scripts/validate_scenario_closure.py --input <record.json>. It checks schema, identity, no-drop sets, and dispositions only. It cannot prove reachability, harm, causation, witness sufficiency, or consumer success. - On a material delta, append a delta record that names the changed boundary and the decision it can change; do not regenerate unrelated families.
What ships with it
2 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.
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.
- 1mo ago Changed · +2 lines · -21 tokens per session d8438d699365
- 1mo ago First seen · 14 lines · 56 tokens per session scan A 4c1553779089
scenario-interaction-closure is a skill published in the GitHub repository Chisiki1/objective-integrity-framework (23 stars, last pushed 8d ago), licensed Apache-2.0. It adds 35 tokens to every session and 278 once invoked, about $0.0001 per session on Opus 5.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-08.
Other skills, from other repositories
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
qa
Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).
test-gen
Generate and verify tests — happy path, edge cases, error paths — using the project's own framework and patterns.
test-harness
Generates pytest test suites with happy path, edge cases, error conditions, fixture scaffolding, mocks, async patterns. Triggers on: "generate tests", "write tests for", "test this function", "create test suite", "pytest for", "unit tests for", "mock strategy for".
voice-agent-test-harness
Drive a fixed suite of spoken tests against a voice agent ("subject") from a co-located machine ("prober"), measure response latency / clarity / accuracy, diff against baseline, and report to the owner over Telegram.
ship-workflow
Resumable shipping lifecycle: reconciles current Git and GitHub facts from any entry (dirty default or feature branch, local commits, published branch, open PR, existing manual or native stack, merged work), commits dirty work as lossless logical commits, publishes or reuses the PR, requires current CI and review…