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 Nolane-x/forge-os --skill verifying-interface-completenessgit clone --depth 1 https://github.com/Nolane-x/forge-osWrote 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/nolane-x/forge-os/verifying-interface-completeness)<a href="https://agentmods.dev/skills/nolane-x/forge-os/verifying-interface-completeness"><img src="https://agentmods.dev/badge/skills/nolane-x/forge-os/verifying-interface-completeness.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.00039 | $0.01455 |
| Opus 5 | $0.00019 | $0.00727 |
| Sonnet 5 | $0.00008 | $0.00291 |
| Haiku 4.5 | $0.00004 | $0.00145 |
Grade A, and why
verifying-interface-completeness 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.
This is a copy
88% identical to testing-service-contracts — 74 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verifying Interface Completeness
Overview
This skill owns one bounded responsibility: verifying interface completeness. Its focus is verifying interface completeness within ux lifecycle boundaries. It converts declared inputs into typed artifacts and reproducible evidence without silently changing product scope.
Trigger
Activate only when the project is in one of these stages: ux-design, all contract preconditions pass, and the router identifies a missing output this skill can produce. Do not activate merely because the skill name resembles the user request.
Required Inputs
product-definitionuser-workflows- Current gate result, open findings, artifact hashes, and invalidation state
- Required tools: none
- Optional tools:
browser - Confirmed human decisions relevant to this scope
Method-Specific Protocol
- Define the exact decision, actors, objects, states, invariants, side effects, and non-goals owned by verifying interface completeness.
- Build a decision table for normal, boundary, invalid, permission, failure, retry, recovery, concurrency, migration, and abuse conditions relevant to verifying interface completeness.
- Apply verifying interface completeness only to direct input artifacts; record assumptions, rejected alternatives, and any human decision still required.
- Trace the resulting contract to user value, security, reliability, cost, operability, and downstream consumers.
- Create reproducible checks that would fail if verifying interface completeness were incomplete or implemented incorrectly.
Procedure
- Read user workflows, constraints, devices, and accessibility needs.
- Define critical journeys and failure recovery before visual styling.
- Define the exact decision, actors, objects, states, invariants, side effects, and non-goals owned by verifying interface completeness.
- Build a decision table for normal, boundary, invalid, permission, failure, retry, recovery, concurrency, migration, and abuse conditions relevant to verifying interface completeness.
- Apply verifying interface completeness only to direct input artifacts; record assumptions, rejected alternatives, and any human decision still required.
- Trace the resulting contract to user value, security, reliability, cost, operability, and downstream consumers.
- Create reproducible checks that would fail if verifying interface completeness were incomplete or implemented incorrectly.
- Specify interaction states, information hierarchy, and feedback.
- Create responsive and accessible behavior contracts.
- Validate critical flows against realistic user tasks.
- Publish UI evidence, open questions, and handoff contracts.
What ships with it
1 file 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.
- 4d ago First seen · 134 lines · 39 tokens per session scan A 4038d786dde5
verifying-interface-completeness is a skill published in the GitHub repository Nolane-x/forge-os (10 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 1,455 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to testing-service-contracts, differing in 74 lines, and is treated as a copy.
Other skills, from other repositories
brand-identity
Define brand strategy, voice, visual direction, tagline, and usage guidelines. Use when creating, refreshing, or standardizing a product or company brand.
canva-automation
Automate Canva tasks via Rube MCP (Composio): designs, exports, folders, brand templates, autofill. Always search tools first for current schemas.
content-typography
A Chinese-language typography and layout guide for content images such as social-media covers, article headers, and posters. It covers headline wording, line breaks, hierarchy, font weight, alignment, spacing, and platform fit.
code-material-gen
A code-based graphics tool that uses HTML and CSS, then renders the result with Playwright, a browser automation tool. It is designed for Chinese text, selectable fonts, and repeatable layouts.
fidelity-gate
Build a UI against a frozen visual reference without drift - an inventory extracted before any code, a relics list, and a gate that MEASURES computed styles on a fixture carrying the reference's own data. Use when a mockup, design spec or screenshot is the contract.
crossbreed
Structural recombination of existing designs. Takes 2-3 prototypes or design approaches and spawns N agents to create HYBRID designs, each with a different "dominant parent" whose architecture leads while grafting specific elements from the others.