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 Sistema2D/FrameCode-VibeWork --skill governance-validatorgit clone --depth 1 https://github.com/Sistema2D/FrameCode-VibeWorkWrote 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/sistema2d/framecode-vibework/governance-validator)<a href="https://agentmods.dev/skills/sistema2d/framecode-vibework/governance-validator"><img src="https://agentmods.dev/badge/skills/sistema2d/framecode-vibework/governance-validator/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/sistema2d/framecode-vibework/governance-validator"><img src="https://agentmods.dev/badge/skills/sistema2d/framecode-vibework/governance-validator.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.00059 | $0.01507 |
| Opus 5.5 | $0.00024 | $0.00603 |
| Sonnet 5.5 | $0.00012 | $0.00301 |
| Haiku 4.5 | $0.00006 | $0.00151 |
Grade A, and why
governance-validator 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 26d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Governance validator
Purpose
Evaluate the human-readable FCVW invariants. The optional script automates deterministic checks; this skill owns interpretation and remediation decisions.
Profiles
clean-template: project-profile placeholders are allowed; application histories and contamination are forbidden.instantiated: required project profiles must be complete.incremental: new violations fail; exact legacy baseline findings are reported but do not block.strict: all applicable findings block.
Inputs
SCHEMAS.md,OWNERSHIP.md,FRAMEWORK_LOCK.md;- physical filesystem;
- active plan and target release;
- optional legacy baseline.
Checks
- Canonical files and ownership metadata.
- Plan status/directory coherence and unique IDs.
- Skill metadata, catalog coverage, and provider-neutral core instructions.
- Framework/application version namespace separation.
- Markdown links and fence balance.
- Wiki IDs, schema, index, freshness, and archive rules.
- Placeholder policy by profile.
- Clean-template contamination.
- Framework lock, release record, and migration coherence.
- The filesystem layout in
OWNERSHIP.mdcovers every path class. - Operational-index and reading-route coverage for every root framework policy, project profile, and declared skill session type.
Optional execution
Installed release:
python FCVW/tools/validate_fcvw.py --root . --profile <profile>
Framework source checkout:
python tools/validate_fcvw.py --root . --profile <profile>
For controlled legacy debt:
Use the matching installed/source tool prefix with --profile incremental --baseline path/to/legacy-baseline.md.
Scripts do not auto-correct historical evidence. Review every proposed remediation and keep the report attached to the active plan or release.
Non-responsibilities
- application runtime tests;
- legal approval;
- destructive cleanup without a plan;
- hiding legacy findings.
Required output
List command/profile, passed checks, new failures, reading-route gaps, baseline findings, corrections, and residual risk.
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.
- 26d ago Changed · +109 lines · +38 tokens per session 22fa8aff9c98
- 1mo ago First seen · 85 lines · 21 tokens per session scan A ca28e6dec2c2
governance-validator is a skill published in the GitHub repository Sistema2D/FrameCode-VibeWork (29 stars, last pushed 24d ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,507 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
writing-tests
Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library. Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests.
emulate-seed
Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS, Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs — full state machines, not mocks. Use when setting up test environments, CI pipelines, integration tests…
error-analysis
Evals-first error analysis for LLM apps: clusters real Langfuse or JSONL traces into a human-confirmed failure taxonomy with counts, then recommends binary pass/fail evals for recurring named modes. Use to learn what to measure before writing evals. Not for CI failures.
architecture-patterns
Architecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right…
testing-e2e
End-to-end testing patterns with Playwright — page objects, AI agent testing, visual regression, accessibility testing with axe-core, and CI integration. Use when writing E2E tests, setting up Playwright, implementing visual regression, or testing accessibility.
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…