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 kotaroyamame/formal-agent-contracts --skill integrated-workflowgit clone --depth 1 https://github.com/kotaroyamame/formal-agent-contractsWrote 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/kotaroyamame/formal-agent-contracts/integrated-workflow)<a href="https://agentmods.dev/skills/kotaroyamame/formal-agent-contracts/integrated-workflow"><img src="https://agentmods.dev/badge/skills/kotaroyamame/formal-agent-contracts/integrated-workflow/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/kotaroyamame/formal-agent-contracts/integrated-workflow"><img src="https://agentmods.dev/badge/skills/kotaroyamame/formal-agent-contracts/integrated-workflow.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.00174 | $0.03617 |
| Opus 5 | $0.00087 | $0.01809 |
| Sonnet 5 | $0.00035 | $0.00723 |
| Haiku 4.5 | $0.00017 | $0.00362 |
Grade A, and why
integrated-workflow 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 10d 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 — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integrated Workflow — End-to-End Formal Agent Development
Overview
This skill orchestrates the full formal development pipeline for multi-agent systems: Define → Verify → Prove → Generate → Test in a single guided session.
Each phase invokes an existing skill, with automated handoff, error recovery, and a final session report summarizing all results.
各フェーズは既存のスキルを呼び出し、フェーズ間の自動ハンドオフ、エラー回復、 最終セッションレポートの生成を行います。
Trigger Conditions
Activate this skill when the user says any of:
- 「統合ワークフローで開発したい」「一気通貫で」「エンドツーエンドで」
- "Run the full workflow", "end-to-end development"
- 「定義から生成まで」「全フェーズ実行して」
- "Define and generate code for an agent"
- Explicitly requests multiple phases in sequence
Workflow Phases
┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐
│ 1.DEFINE │───>│ 2.VERIFY │───>│ 3.PROVE │───>│ 4.GENERATE│───>│ 5.TEST │
│ │ │ │ │ (optional)│ │ │ │ │
└──────────┘ └──────────┘ └──────────┘ └──────────┘ └──────────┘
│ │ │ │ │
▼ ▼ ▼ ▼ ▼
.vdmsl PO list SMT results TS/Python Test
file + report + proofs code report
Execution Flow
Phase 0: Session Setup
-
Greet the user and explain the integrated workflow briefly:
「統合ワークフロー」では、エージェントの契約定義から実装コード生成まで、 5つのフェーズを順番に実行します。途中でスキップや中断も可能です。
-
Gather session parameters:
- Agent name: What agent are we defining?
- Starting point: New definition, existing
.vdmslfile, or natural language spec (MD)?- If existing
.vdmslfile: skip to Phase 2 (Verify) - If natural language MD file: invoke
import-natural-specfirst to convert to VDM-SL
- If existing
- Target language: TypeScript, Python, or both?
- SMT verification: Include Z3 automated proving? (requires Z3 installed)
-
Initialize session state (track mentally, no files needed):
agent_name: <name> vdmsl_path: <to be determined> target_lang: ts | py | both smt_enabled: true | false phases_completed: []
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.
- 10d ago First seen · 360 lines · 174 tokens per session scan A 9bb99b8aac14
integrated-workflow is a skill published in the GitHub repository kotaroyamame/formal-agent-contracts (1 stars, last pushed 2mo ago), licensed MIT. It adds 174 tokens to every session and 3,617 once invoked, about $0.0009 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
verify-gates
Runs the mechanical quality gates that the arcgentic state machine requires for state transitions. Invoked indirectly by transition.sh OR directly by orchestrator agent before declaring a state transition. Use when about to call transition.sh OR when manually verifying that a round artifact meets the gate criteria.…
auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog.
workflow
Run the complete 5-step development workflow: focus problem → prevent over-development → test-first (TDD) → document → smart commit. Use when starting a new feature, or when the user runs /workflow or asks for the full development flow.
test-runner
Test execution reference: framework detection (pytest/jest/vitest/go/cargo/junit) and correct run/coverage commands, plus failure-analysis steps. Use when running tests, analyzing test failures, or verifying coverage after code changes.
test-first
Drive one feature through a strict TDD Red-Green-Refactor cycle with checklists for each phase. Use when implementing new functionality test-first, or when the user runs /test-first.
linked-intent-dev
Guide for linked-intent development (LID). Consult for ALL code changes. Walks changes through a mode-aware six-phase workflow (HLD → LLD → EARS → intent-narrowing edge audit → tests-first → code) with mandatory stops between each phase. Bugs walk the arrow like any other change — no short-circuit. Enforces cascade…