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.
git clone --depth 1 https://github.com/vibeic/vibe-icWrote 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/commands/vibeic/vibe-ic/_anti_fabrication_rules)<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.
<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>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.00000 | $0.01197 |
| Opus 5.5 | $0.00000 | $0.00479 |
| Sonnet 5.5 | $0.00000 | $0.00239 |
| Haiku 4.5 | $0.00000 | $0.00120 |
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 2mo 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 — 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)
-
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). -
Provenance entries carry SHA256 of every output:
provenance.jsonlrows must include"outputs": {"<rel>": "sha256:<64hex>", ...}. Synthetic timestamps (every entry on:00second boundary, regular gaps) will be flagged byprovenance_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 addoutputs_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. -
reports/root holds only 2 markdown files —final_summary.md+chip_specific_summary.md(produced byfinal_report_generate.py). Retry verdicts, run logs, agent notes route through_pl.report_path()intoreports/orchestrator/logs/orreports/audit/. Loose files atreports/root failreports_subfolder_taxonomy_check. -
Step-internal gate FAIL ⇒ verdict FAIL. No
Overall: PASSwhile a sub-gate (cdc / formal / lint / etc.) inside any step is FAIL. Bubble up. -
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.
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.
- 2mo ago First seen · 89 lines · 0 tokens per session scan A 7365a5c33c91
_anti_fabrication_rules is a command published in the GitHub repository vibeic/vibe-ic (28 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.
Other commands, from other repositories
pcb-new
Start a new PCB project from a text description. Sources parts, generates a wired .kicadpcb, and hands off to EasyEDA for routing + JLCPCB ordering.
pcb-from-bom
Start a PCB project from an existing LCSC BOM file (CSV with C-numbers) and a design-intent description.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.