_anti_fabrication_rules

_anti_fabrication_rules is a command for Claude Code from vibeic/vibe-ic. It costs 0 tokens per session (1,197 once invoked), scanned A, original, Apache-2.0.

A shared set of rules for preventing fabricated evidence or false passes in hardware-design pipeline commands.

In plain words
What is it for?
Use it whenever running the covered Phase 2, Phase 3, Phase 23, or Vibe-IC commands and checking their deliverables and provenance.
Why use it?
It requires real canonical files, complete SHA-256 output records, and honest disclosure of moved or removed outputs so reports cannot hide missing work.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the vibe-ic plugin — 70 skills, 8 commands, 8 agents, 2 hooks, 1 MCP server shipped together

Good fit Use it whenever running the covered Phase 2, Phase 3, Phase 23, or Vibe-IC commands and checking their deliverables and provenance.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/vibeic/vibe-ic/_anti_fabrication_rules
Install

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.

Clone the repo
git clone --depth 1 https://github.com/vibeic/vibe-ic

Made for: Claude Code.

Or install vibe-ic, the plugin that ships this one along with the rest of its 70 skills, 8 commands, 8 agents, 2 hooks, 1 MCP server.

Wrote 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.

agentmods badge for _anti_fabrication_rules

README.md
[![agentmods](https://agentmods.dev/badge/commands/vibeic/vibe-ic/_anti_fabrication_rules/github.svg)](https://agentmods.dev/commands/vibeic/vibe-ic/_anti_fabrication_rules)
Your own site
<a href="https://agentmods.dev/commands/vibeic/vibe-ic/_anti_fabrication_rules"><img src="https://agentmods.dev/badge/commands/vibeic/vibe-ic/_anti_fabrication_rules/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.

agentmods 80×15 button for _anti_fabrication_rules

Your own site · 80×15
<a href="https://agentmods.dev/commands/vibeic/vibe-ic/_anti_fabrication_rules"><img src="https://agentmods.dev/badge/commands/vibeic/vibe-ic/_anti_fabrication_rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,197 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01197
Opus 5 $0.00000 $0.00598
Sonnet 5 $0.00000 $0.00239
Haiku 4.5 $0.00000 $0.00120

Measured 11d ago against content hash 7365a5c33c91, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

_anti_fabrication_rules 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 11d 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.

vibe-ic-marketplace/plugins/vibe-ic/commands/_anti_fabrication_rules.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

v1.6.30 Anti-fabrication Rules — shared appendix

Codified after the v10627 / v10627-vendor false-PASS comparison. Inlined into every phase2 / phase2 / phase3 / phase23 / vibe-ic-all command so that any fresh agent invoking those commands sees the same hard rules.


5 hard rules (any one violated ⇒ verdict-FAIL)

  1. Real file, no symlink in canonical deliverable trees: phase3/stage4/**, phase3/mixed_signal/**, phase2/stage1/fpga/**, analog/hardmacro/**. Foundry-shipped references that must be symlinks: declare in <project>/.canonical_symlink_allowlist (one path per line).

  2. Provenance entries carry SHA256 of every output: provenance.jsonl rows must include "outputs": {"<rel>": "sha256:<64hex>", ...}. Synthetic timestamps (every entry on :00 second boundary, regular gaps) will be flagged by provenance_output_hash_completeness_check (roadmap). Empty is honest; fabricated is dishonest. An output the publish step did not ship is DISCLOSED, never deleted (#414): keep the row and its digest and add outputs_relocated_at_publish / outputs_pruned_at_publish + outputs_pruned_reason. Deleting the row to quiet the gate restores the dangling pointer those keys exist to remove.

  3. reports/ root holds only 2 markdown filesfinal_summary.md + chip_specific_summary.md (produced by final_report_generate.py). Retry verdicts, run logs, agent notes route through _pl.report_path() into reports/orchestrator/logs/ or reports/audit/. Loose files at reports/ root fail reports_subfolder_taxonomy_check.

  4. Step-internal gate FAIL ⇒ verdict FAIL. No Overall: PASS while a sub-gate (cdc / formal / lint / etc.) inside any step is FAIL. Bubble up.

  5. Final report carries a SHA256 attestation table of every canonical artefact (SOF / GDS / synth-netlist / LEF / Liberty / sign-off reports). Without that table, "PASS" is unverifiable and counts as incomplete.

Read the full file on GitHub · 89 lines

Changes

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.

  1. 11d ago First seen · 89 lines · 0 tokens per session scan A 7365a5c33c91

Subscribe to this mod's changes

_anti_fabrication_rules is a command published in the GitHub repository vibeic/vibe-ic (23 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,197 tokens. 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.