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 retroactive-instantiationgit 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/retroactive-instantiation)<a href="https://agentmods.dev/skills/sistema2d/framecode-vibework/retroactive-instantiation"><img src="https://agentmods.dev/badge/skills/sistema2d/framecode-vibework/retroactive-instantiation.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 53 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 54 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00018 | $0.00877 |
| Opus 5 | $0.00009 | $0.00439 |
| Sonnet 5 | $0.00004 | $0.00175 |
| Haiku 4.5 | $0.00002 | $0.00088 |
Grade A, and why
retroactive-instantiation 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 8d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL: Retroactive Instantiation
High-density activation guide for adopting FrameCode VibeWork inside an existing, advanced, legacy, or partially governed application.
Purpose
Adopt FCVW non-destructively in an existing application, separating observed project truth from framework policy and from pre-adoption history.
Activation Triggers
Load this skill when:
- the user asks for retroactive FCVW adoption in an existing application;
- the repository already contains application code before FCVW is installed;
- an older or partial
FCVW/structure must be migrated forward; - the task mentions "instanciação retroativa", "adotar FCVW", "migrar framework antigo", "legacy app", "advanced app", or "governance retrofit".
Use project-instantiation instead for blank or fresh Phase 0 projects.
Mandatory Source of Truth
Read and follow FCVW/RETROACTIVE_INSTANTIATION.md.
This skill is only the JIT trigger and compact checklist. Do not duplicate or override the canonical workflow.
Inputs
Existing repository and history, current application documentation, RETROACTIVE_INSTANTIATION.md, OWNERSHIP.md, framework lock and migration, project authority, and baseline build/test/deploy evidence.
Execution Checklist
- Read
AGENTS.md,FCVW/RETROACTIVE_INSTANTIATION.md, andFCVW/CONTEXT_MAP.md. - Inspect the current repository and classify it:
- Case A: no FCVW present;
- Case B: older FCVW present;
- Case C: partial or inconsistent FCVW present.
- Create or update
FCVW/Plans/in_progress/P2-R4-{date}-retroactive-instantiation.md. - Preserve application files first: source code, root README, runtime configs, data, tests, deployment files, and existing docs.
- Load
skills/code-hygiene-refactor/SKILL.mdand record a non-destructive hygiene triage: duplicates, stale files, dead code candidates, catch-all modules, and monolith candidates. - Load
skills/anti-monolith-guard/SKILL.mdfor every identified monolith that will receive new changes. - Import, repair, or migrate FCVW under
FCVW/using non-destructive merges. - Fill project documents from evidence; use
To be definedfor missing facts. - Preserve historical plans, changelogs, troubleshooting records, decisions, audits, and wiki pages.
- Add a changelog fragment and validation evidence; regenerate filesystem paths when changed, and create wiki/session records only when their promotion or handoff criteria are met.
- Run safe local tests and structural checks; record limitations instead of inventing results.
- Move the plan to the final status folder only after validation is recorded.
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.
- 8d ago First seen · 79 lines · 18 tokens per session scan A 3cc3c5a0939d
retroactive-instantiation is a skill published in the GitHub repository Sistema2D/FrameCode-VibeWork (23 stars, last pushed 7d ago), licensed Apache-2.0. It adds 18 tokens to every session and 877 once invoked, about $0.0001 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-30.
Other skills, from other repositories
evaluate-pattern-adoption
Run or plan this repository's pattern-adoption evidence evaluation locally with signed-in Codex agents. Use when asked to refresh stale evidence, assess stable or exploratory patterns, evaluate one or all catalog patterns, discover possible new patterns, or prepare a reviewable evidence PR without model-backed GitHub…
traceability-gate
Enforces parent-link lineage across requirement layers.
Compliance Checker
Check regulatory compliance across finance, tax, employment, data privacy, and industry-specific requirements.
wendao
Internal guardian skill for creating and editing Wendao DocOS documentation.
Advisory Board Builder
Recruit, structure, and manage advisory boards for strategic guidance.
Board Meeting Prep
Prepare board meeting decks, updates, and materials for effective governance.