maxtac-source-invariant-loop

Model and audit security invariants in source code for violations.

12|Updated Jun 1, 2026

Search Tags:#code analysis #vulnerability assessment #security review #security invariants #source code audit

Ready to run

npx skills add https://github.com/philo-groves/MaxTAC --skill maxtac-source-invariant-loop

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: maxtac-source-invariant-loop
Source: https://github.com/philo-groves/MaxTAC/tree/main/plugins/maxtac-source/skills/maxtac-source-invariant-loop
Command: npx skills add https://github.com/philo-groves/MaxTAC --skill maxtac-source-invariant-loop

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires maxtac-core, maxtac-source, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the need to model security invariants for code subsystems, map guards, sinks, entrypoints, callers, and proof obligations, then perform targeted audits for invariant violations in source or decompiler output.

Core Features & Use Cases

Invariant Modeling: Maps security invariants in source or decompiler output.
Targeted Audits: Audits for invariant violations with evidence-based dispositions.
Use Case: Ideal for source code reviews where it's critical to ensure that security invariants are upheld and that potential vulnerabilities are identified.

Quick Start

Use the maxtac-source-invariant-loop skill to create a loop state for source invariants in your codebase with the command: 'maxtac-core-modeling' to create a Core model.

Frequently Asked Questions about maxtac-source-invariant-loop

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

FAQPage Schema

How do I audit source code for security invariant violations?▼

Security invariant modeling maps guards, sinks, entrypoints, and proof obligations in source or decompiler output to establish a baseline for security audits. It identifies potential vulnerabilities by tracking these critical code paths.

How do I map guards and sinks for a vulnerability assessment?▼

To map guards and sinks for a vulnerability assessment, model security invariants in source or decompiler output to trace callers and entrypoints. This identifies where proof obligations are violated and highlights potential vulnerabilities.

Can I use source invariant modeling on decompiler output?▼

Yes, source invariant modeling works on decompiler output. It maps security invariants, guards, and sinks directly from decompiled code, enabling targeted audits to identify invariant violations and enforce security policies.

What is the best way to enforce security policies during a code review?▼

The best way to enforce security policies during a code review is to model security invariants and audit for violations using evidence-based dispositions. This targets exact code subsystems where security policies are breached.

Do I need maxtac-core to audit security invariants?▼

Yes, you need maxtac-core and maxtac-source to audit security invariants. You use the maxtac-core-modeling command to create a core model and initialize the loop state required for targeted source audits.