Code Forensics Stinger

Organization

legioncodeinc

code-forensics-stinger

Review software vendor engagements using contracts, invoices, messages and delivery records. Produce cited evidence drafts for human or counsel review. Read README.md for the guide map.

Overview

Publisher	legioncodeinc
Repository	`vibe-coding-tools`
Skill name	`code-forensics-stinger`
Stars	94
Forks	44
Bundled files	46
License	AGPL-3.0-or-later
Links	Skill source Repository

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.
46 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by legioncodeinc on GitHub. Read the source before you install it.

Installation

Install the Code Forensics Stinger 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/legioncodeinc/vibe-coding-tools/tree/main/plugins/code-audit-tools/skills/code-forensics-stinger
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/legioncodeinc/vibe-coding-tools/tree/main/plugins/code-audit-tools/skills/code-forensics-stinger

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

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/legioncodeinc/vibe-coding-tools.git /tmp/vibe-coding-tools
mkdir -p .claude/skills
cp -r /tmp/vibe-coding-tools/plugins/code-audit-tools/skills/code-forensics-stinger .claude/skills/code-forensics-stinger

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

Use it in TypingMind

Enable Code Forensics Stinger 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 Code Forensics Stinger 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 Code Forensics Stinger 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.

Code Forensics Stinger

Use this skill when the user requests a forensic review of a software or agency engagement and can supply source records. Ask who the parties are and what happened. Never recognize a new matter by assuming a named party, country, price, jurisdiction or misconduct pattern from another matter.

Read README.md and principles first. For routine code review, route to the relevant engineering specialist. Legal determinations belong to counsel.

Workflow

Phase	Guide	Result
0	Intake	Agreed scope, materials and private case workspace
1	Email	Source-indexed communication records
2	Invoices	Documented billing and separate estimates
3	Git	Acquired history with stated limits
4	Dependencies	Version evidence and dated advisories
5	Logs	Observed activity and coverage gaps
6	Marketing	Contracted outputs and comparable metrics
7	Synthesis	Author-supplied report sections and cited output
8	Review letters	Combined draft for counsel review

Assess each phase for relevance. Record absent materials without fabricating findings. Keep source records and working notes separate from the validated renderer input.

Rendering

The input contract and JSON Schema describe case-facts.json. It contains matter metadata, an evidence register and authored document sections. It is not an automatic investigation accumulator. Python helpers do not populate it automatically.

Kind	Entry point
master	`scripts/build_master_report.js`
agency	`scripts/build_agency_report.js`
attorney	`scripts/build_attorney_memo.js`
plain_language	`scripts/build_plain_language.js`
pre_litigation	`scripts/build_pre_litigation.js`

Every invocation requires --case-facts FILE --out-dir DIR. Default format is docx; use --format markdown for Markdown. Missing input or a missing selected document refuses before any output directory is created. Existing output files are never overwritten. Generate revisions in a new private directory.

Review standard

Every material claim has source IDs and an evidence tier. Estimates are separate from observed facts. Do not promise a fixed page count, number of letters, spreadsheet tabs, outcome, recovery amount or litigation readiness. The renderer copies supplied text; review it before sharing. Public training fixtures are explicitly fictional and must never be used as a real case's facts.

Critical Directive

Read relevant guides and inspect the actual source before relying on a tool. Supplement missing research with current authoritative sources. Preserve originals unmodified. No legal advice, assumed privilege, automatic external sends or unapproved live actions. Security and Quality review apply before any authorized commit; the controlling user must explicitly authorize commit, push, publication and distribution.

Bundled files

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

Frequently asked questions

What does the Code Forensics Stinger AI skill do?

Review software vendor engagements using contracts, invoices, messages and delivery records. Produce cited evidence drafts for human or counsel review. Read README.md for the guide map.

Why use Code Forensics Stinger on TypingMind?

Because you install it once and use it with any model. Code Forensics Stinger 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 Code Forensics Stinger in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/legioncodeinc/vibe-coding-tools/tree/main/plugins/code-audit-tools/skills/code-forensics-stinger. 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 Code Forensics Stinger?

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 Code Forensics Stinger?

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

Is the Code Forensics Stinger AI skill free?

Yes. It is published on GitHub by legioncodeinc under the AGPL-3.0-or-later license. 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

Deslop

openclaw

OrganizationPopular

Diff-scoped AI-slop cleanup pass: strip comment slop, defensive-check slop, type-laundering, and style drift from the current branch diff before autoreview.

Discord Clawd

Use to talk to the Discord-backed OpenClaw agent/session; not for archive search.

Discrawl

Discord archive: search, sync freshness, DMs, summaries, TUI, repo/release work.

Gitcrawl

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

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Code Forensics Stinger

Workflow

Rendering

Review standard

Critical Directive

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now