newmanxbt/sealevel-guard · Archived

token-invariants

Detects whether token and vault logic can violate economic or accounting assumptions another agent would rely on. Internal specialist module for token invariant review.

First seen Mar 27, 2026

Installation

$ npx skills add newmanxbt/sealevel-guard --skill token-invariants

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from newmanxbt/sealevel-guard.

npx skills add newmanxbt/sealevel-guard

Browse all from newmanxbt/sealevel-guard

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,092 B
  • docs SUMMARY.md 192 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Token Invariants

Token flow and vault invariant review skill.

Purpose

Detect whether token and vault logic can violate the economic or accounting assumptions another agent would rely on.

Focus

This skill is responsible for:

  • mint and burn authority issues,
  • withdrawal control failures,
  • accounting drift,
  • redemption mismatch,
  • fee logic mismatch,
  • and vault balance or share inconsistency.

What To Look For

  • token supply changes without robust authority checks
  • withdrawal paths that do not match accounting assumptions
  • fee or redemption math that can create trust-breaking imbalance
  • vault logic that trusts stale or weakly-bound state

Output Shape

Each finding should explain:

  • what invariant the system seems to promise,
  • how code can violate it,
  • and why a downstream agent should treat that as a trust concern.