nitzzzu

Penetration testing tools for the CodeAgent — network scanning, service enumeration, and vulnerability checks

Obsidian Local REST API tools for the CodeAgent — manage vault notes, search, and metadata

Frida dynamic instrumentation tools for the CodeAgent — mobile app analysis and SSL unpinning

DuckDB in-process analytics tools for the CodeAgent — SQL on CSV/Parquet/JSON without a server

Supabase client tools for the CodeAgent — database CRUD, auth, storage, and edge functions

OSINT reconnaissance tools for the CodeAgent — domain, IP, email, and social media intelligence

Use BEFORE any creative work — creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements, and design before implementation.

Use when completing tasks, implementing major features, or before merging — request a thorough review that checks spec compliance, code quality, security, and tests.

Research a topic, library, codebase, or question using the local agentic-fetch service. Use this skill any time the task requires reading more than one URL, searching documentation, comparing sources, or building an answer from web content. Beats raw WebFetch when you need parallelism, persistent caching, BM25 search across what you've already read, or targeted line/grep access to long pages.

Take the community pulse on a topic, library, or trend by aggregating Reddit + HackerNews + GitHub trending via the local agentic-fetch service. Use this when the user asks "what are people saying about X", "is X getting popular", "what's hot in <domain> right now", "should I bet on X", "find me good discussions about X", or wants to track how sentiment / attention is changing over time. Different from the `research` skill: that one extracts facts, this one surfaces opinions, signals, and momentum.