License Robustness Audit

Community

ptn1411

license-robustness-audit

Defensive audit of a license/entitlement/activation mechanism on software you own or are authorized to test. Maps the validation surface, flags design weaknesses that make checks easy to abuse, and produces hardening guidance plus an allow/deny test scaffold — without generating keygens, patches, or bypasses.

Overview

Publisher	ptn1411
Repository	`skill`
Skill name	`license-robustness-audit`
Stars	275
Forks	133
Bundled files	2
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by ptn1411 on GitHub. Read the source before you install it.

Installation

Install the License Robustness Audit AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/ptn1411/skill/tree/main/license-robustness-audit
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/ptn1411/skill.git /tmp/skill
mkdir -p .claude/skills
cp -r /tmp/skill/license-robustness-audit .claude/skills/license-robustness-audit

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable License Robustness Audit in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads License Robustness Audit on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so License Robustness Audit is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

License Robustness Audit

Test how hard your licensing is to abuse — defensively. Map where validation happens, identify the design weaknesses that would let it be bypassed, and get a concrete hardening plan and tests for the legitimate allow/deny path.

Language rule: All skill instructions use English. Final summary presented to the user must be in Vietnamese.

0. Authorization & Boundary

Operates under MASTER_POLICY.md §1-§2. Use only on software you own or are authorized to assess.

This is the defensive counterpart to keygen/patch/bypass. It answers "is my license easy to bypass, and how do I harden it?" It does not produce a working keygen, license file, patch, or repacked binary — those remain out of scope by policy. Instead it yields an abuse-case analysis and source-level fixes.

Sibling skill	When
dotnet-decompiler	Recover .NET source first, then audit it here
java-decompiler	Recover Java source first
electron-app-analyzer	Recover Electron JS first
network-interceptor	Confirm whether validation calls a server

Step 1 — Point it at your source

Run over an owned source tree or a recovered/decompiled one:

powershell
python license-robustness-audit\scripts\audit_license.py <source_dir> --out output\license-audit

bash
python license-robustness-audit/scripts/audit_license.py output/dotnet-decompiled --out output/license-audit

It scans .cs/.js/.ts/.java/.py/.cpp/.go/... files for licensing logic.

Step 2 — Read the audit

Outputs in --out:

LICENSE_AUDIT.md — validation surface, weaknesses (abuse-case view, severity-ranked), a hardening plan, and a test plan.
ATTACK_PATH.md — design-level attack paths for a red-team write-up: a mermaid flow diagram of where the decision breaks, plus per-weakness precondition → technique class → effect → control. Descriptive findings, not a working bypass/keygen/patch.
license_findings.json — structured findings.
test_license_behavior.py — a pytest scaffold; wire evaluate_license() to your real check to prove valid→allow / expired/tampered/missing→deny.

What it flags (design weaknesses)

Category	Why it's abusable
Client-side validation gate	A client-held check can be observed and forced true
Bare boolean license decision	One-instruction bypass target
Hardcoded secret / signing key	Shipped secrets let an attacker mint valid licenses
Embedded public key + local verify	Verify path + key can be swapped together
Static key comparison	Accept condition trivially discoverable
Weak hash (MD5/SHA-1) in license path	Collision-prone integrity
Local trial/activation state	Resettable to extend usage
No server-side validation signal	Whole decision is local ⇒ tamperable

Hardening direction (the fix, not the bypass)

Authoritative check server-side; client only renders the signed decision.
Signed, short-lived entitlements (Ed25519 / RSA-PSS): user, features, expiry.
No secrets in the client; keep signing keys server-side and rotate them.
Bind trial/activation to an account/device server-side; local files are cache only.
Fail closed on any error; add tamper-evidence and verification telemetry.

Use the generated test scaffold to lock in correct allow/deny behavior as a regression guard.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

references/license_hardening.md2 KB
scripts/audit_license.py15 KB

Frequently asked questions

What does the License Robustness Audit AI skill do?

Why use License Robustness Audit on TypingMind?

Because you install it once and use it with any model. License Robustness Audit is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install License Robustness Audit in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ptn1411/skill/tree/main/license-robustness-audit. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use License Robustness Audit?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with License Robustness Audit?

As many as you like. As long as a model supports skills, you can use License Robustness Audit with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the License Robustness Audit AI skill free?

It is published on GitHub by ptn1411. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Gitcrawl

openclaw

OrganizationPopular

GitHub archive: issue/PR search, sync freshness, duplicate clusters, current GitHub handoff, and Gitcrawl repo work.

Graincrawl

Granola archive: search, sync freshness, notes, transcripts, panels, SQL counts, and Graincrawl repo work.

Openclaw Changelog Update

openclaw

OrganizationPopular

Regenerate OpenClaw release changelog sections from git history before beta, stable, or extended-stable releases.

Openclaw Ci Limits

Manage OpenClaw GitHub Actions and Blacksmith CI capacity, runner-registration budgets, fanout caps, main-push single-flight, shard sizing, hosted-runner offload, queue health, and safe…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

License Robustness Audit

0. Authorization & Boundary

Step 1 — Point it at your source

Step 2 — Read the audit

What it flags (design weaknesses)

Hardening direction (the fix, not the bypass)

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now