Skip to content
cccskills

Alex Greenshpun

@alexgreensh

7 skills3 repositories 2.7K

Repositories

Skills (7)

Refine in search

tldr

Free

Compress a document, thread, transcript, or pasted text into a scannable TL;DR.

The English summary is being prepared. Showing the original description.

alexgreensh/attention-span1.5KUpdated Oct 22, 2026

Answer in the ADHD-friendly Attention-kind style for the rest of this chat.

The English summary is being prepared. Showing the original description.

alexgreensh/attention-span1.5KUpdated Oct 22, 2026

Answer in the terse, zero-warmth Spartan style for the rest of this chat.

The English summary is being prepared. Showing the original description.

alexgreensh/attention-span1.5KUpdated Oct 22, 2026

Answer in the Rundown briefing style (TL;DR + checklist + numbered choices).

The English summary is being prepared. Showing the original description.

alexgreensh/attention-span1.5KUpdated Oct 22, 2026

Code-drawn stills, drawing timelapses, films, explainers and interactive web animations in 32 styles, with composed scores. Matches a reference style, keeps characters consistent, teaches drawing. Deterministic, no generated assets.

The English summary is being prepared. Showing the original description.

alexgreensh/anidoodle1KUpdated Oct 18, 2026

Security forensics for git repos, AI skills, and MCP servers. Audits dependencies, detects prompt injection, credential theft, runtime dynamism, manifest drift, known CVEs, CISA KEV (actively exploited) vulns, and 2026 attack patterns. Not for fixing vulnerabilities or pentesting.

The English summary is being prepared. Showing the original description.

alexgreensh/repo-forensics194Updated Oct 23, 2026

Cross-agent self-inspection of your AI-agent stack. Audits skills, MCP servers, hooks, plugins, commands, credentials, and memory files across Claude Code, Codex, OpenClaw, and NanoClaw. Produces a structured inventory and narrative briefing with cross-ecosystem risk analysis. Use when the user asks to audit their own setup, check what they have installed, review their agent stack security posture, or understand cross-tool interactions. Use when a user has accumulated skills/plugins/MCP servers over time and wants visibility into their attack surface. Use after installing new skills or plugins. Do NOT use for vetting external code before install (that is repo-forensics). Do NOT use for incident response during active attacks. Do NOT use for fixing or patching vulnerabilities (forensify is read-only).

The English summary is being prepared. Showing the original description.

alexgreensh/repo-forensics194Updated Oct 23, 2026

Is this your account? Link GitHub to bring it onto your creator page (Japanese)