base-in-reality

Audits repository code, architecture, and business logic against fetched academic and standards sources.

1|Updated May 28, 2026
One-click install
npx skills add https://github.com/dhanesh/agent-skills --skill base-in-reality-dhanesh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: base-in-reality
Source: https://github.com/dhanesh/agent-skills/tree/main/base-in-reality
Command: npx skills add https://github.com/dhanesh/agent-skills --skill base-in-reality-dhanesh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Codebases often embed algorithms, architectural choices, or business rules that silently violate established norms, standards, or best practices, and AI-generated audits frequently cite fabricated or remembered sources. This Skill validates a repository against real-world knowledge from scholarly APIs and standards bodies, and enforces that every finding is tied to a citation actually fetched during the session. ## Core Features & Use Cases - Research-grounded claim verification: Extracts falsifiable claims across algorithm, architecture, and business-logic layers, routes each to the right source class (arxiv, PubMed, OpenAlex, Crossref, Semantic Scholar, NIST, IETF/RFC, OWASP, ISO, sector regulators), and verifies against fetched evidence. - Anti-fabrication enforcement: fetch_sources.py appends every retrieved URL/DOI to an evidence log, and report_lint.py rejects any citation flagged fetched that never appears in it; ungrounded claims are reported as UNCONFIRMED, never as violations. - Adversarial refutation gate: Candidate VIOLATION/DEVIATION findings must survive independent refuter passes across correctness, citation-applicability, and severity lenses, with severity-aware vote aggregation enforced by the linter. - Use Case: Ask whether your lending module's APR calculation follows Regulation Z or whether your password hashing follows NIST SP 800-63B, and receive a severity-graded Markdown report where every verdict carries a real, fetched citation. ## Quick Start Ask the agent to run a base-in-reality audit on this repository and report any algorithms, architectural choices, or business rules that violate established standards with cited sources.

Frequently Asked Questions about base-in-reality

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a codebase against academic papers and standards?▼

Run the audit procedure: it detects the repo's domain, extracts falsifiable claims across algorithm, architecture, and business layers, routes each to sources like arxiv, PubMed, NIST, or OWASP, and verifies against fetched evidence. The output is a severity-graded Markdown report with citations.

How does the audit prevent fabricated citations?▼

fetch_sources.py appends every retrieved URL and DOI to a session evidence log, and report_lint.py --evidence rejects any citation flagged fetched that appears nowhere in that log. Ungrounded claims are downgraded to UNCONFIRMED rather than reported as violations.

Can I audit only part of a repository or one layer?▼

Yes. Use --layer algo|arch|biz to restrict to one layer, --since <ref> to audit only a diff, --domain to override auto-detection, and --max-claims to cap extraction. Dropped claims are listed in the report so coverage is never overstated.

Does the audit modify my source code?▼

No, it is read-only by default and only writes its report under docs/base-in-reality/. The optional --annotate flag inserts comment markers at finding locations but never changes logic, and you can request the report in-conversation instead.

What are the limitations of a research-grounded code audit?▼

It reasons about norms and best practices, not syntax, so it is not a linter, SAST tool, or CVE scanner. Some sources like JSTOR and ISO are abstract-only, deep verification is token-heavy on large repos, and contested practices are reported as DEVIATION rather than VIOLATION.