
Metatron Pentest Assistant
Run local AI-assisted recon and vulnerability tracking on Parrot OS with Ollama, MariaDB history, and exportable reports—no cloud API keys.
Overview
METATRON Pentest Assistant is an agent skill for the Ship phase that runs local AI-assisted penetration testing with Ollama, MariaDB scan history, and recon tool orchestration on Parrot OS.
Install
npx skills add https://github.com/aradotso/trending-skills --skill metatron-pentest-assistantWhat is this skill?
- CLI assistant on Parrot OS with local metatron-qwen via Ollama—no cloud LLM API keys
- Orchestrates nmap, whois, whatweb, curl, dig, and nikto through tools.py runners
- MariaDB spine stores scan history, vulnerabilities, fixes, exploits, and summaries per sl_no
- Agentic LLM loop in llm.py plus DuckDuckGo and CVE lookup in search.py without API keys
- PDF and HTML vulnerability export from accumulated scan history
- 6 core modules: metatron.py, db.py, tools.py, llm.py, search.py, Modelfile
- 6 recon tools referenced: nmap, whois, whatweb, curl, dig, nikto
Adoption & trust: 553 installs on skills.sh; 31 GitHub stars; 0/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need structured pentest recon and vulnerability history without sending target data to cloud LLMs or juggling disconnected terminal commands.
Who is it for?
Builders on Parrot OS who already have authorization to test targets and want a local Ollama analyst plus nmap-class tooling in one CLI workflow.
Skip if: Casual prod scanning without permission, teams that cannot run Linux recon tooling, or beginners who only need a passive dependency audit checklist.
When should I use this skill?
When triggers match: set up METATRON, run automated pentest with AI, configure Ollama and MariaDB, add recon scans, export reports, troubleshoot model or DB, extend custom tools, or query scan history.
What do I get? / Deliverables
Configured METATRON stack runs orchestrated scans, persists findings in MariaDB, and exports PDF or HTML reports from queryable history.
- MariaDB-backed scan and vulnerability records
- PDF or HTML vulnerability export
- Queryable scan history by serial identifier
Recommended Skills
Journey fit
How it compares
Local CLI pentest orchestration with MariaDB history—not a hosted SaaS scanner or a generic secure-coding linter skill.
Common Questions / FAQ
Who is metatron-pentest-assistant for?
Security-curious indie developers and pentest learners on Parrot OS who want agent-guided setup, scans, DB queries, and exports using local Ollama.
When should I use metatron-pentest-assistant?
During ship security when hardening APIs or SaaS before launch, when extending custom recon modules, or when troubleshooting Ollama model and MariaDB integration for scan history.
Is metatron-pentest-assistant safe to install?
It enables network recon and shell-backed tools on targets you must be authorized to test; review the Security Audits panel on this page and your legal scope before install.
SKILL.md
READMESKILL.md - Metatron Pentest Assistant
# METATRON Penetration Testing Assistant > Skill by [ara.so](https://ara.so) — Daily 2026 Skills collection. METATRON is a CLI-based AI penetration testing assistant that runs entirely locally — no cloud, no API keys. It orchestrates recon tools (nmap, whois, whatweb, curl, dig, nikto), feeds results to a locally running fine-tuned LLM (`metatron-qwen` via Ollama), and stores all findings in MariaDB with full scan history, vulnerability tracking, and PDF/HTML export. --- ## Architecture Overview ``` metatron.py ← CLI entry point, main menu, scan orchestration db.py ← MariaDB CRUD (history, vulns, fixes, exploits, summary) tools.py ← Recon tool runners (nmap, whois, whatweb, curl, dig, nikto) llm.py ← Ollama interface, agentic loop, AI tool dispatch search.py ← DuckDuckGo search + CVE lookup (no API key) Modelfile ← Custom metatron-qwen model config ``` **Database spine:** every scan creates a `sl_no` in `history`; all other tables link via `sl_no`. --- ## Installation ### 1. Clone and set up Python environment ```bash git clone https://github.com/sooryathejas/METATRON.git cd METATRON python3 -m venv venv source venv/bin/activate pip install -r requirements.txt ``` ### 2. Install system recon tools ```bash sudo apt install nmap whois whatweb curl dnsutils nikto ``` ### 3. Install Ollama and pull base model ```bash curl -fsSL https://ollama.com/install.sh | sh # 8GB+ RAM: ollama pull huihui_ai/qwen3.5-abliterated:9b # <8GB RAM — use 4b and edit Modelfile FROM line accordingly: ollama pull huihui_ai/qwen3.5-abliterated:4b ``` ### 4. Build the custom metatron-qwen model ```bash ollama create metatron-qwen -f Modelfile ollama list # verify metatron-qwen appears ``` **Modelfile** (the repo ships this — key parameters): ``` FROM huihui_ai/qwen3.5-abliterated:9b PARAMETER num_ctx 16384 PARAMETER temperature 0.7 PARAMETER top_k 10 PARAMETER top_p 0.9 ``` To use 4b instead, edit `Modelfile`: ``` FROM huihui_ai/qwen3.5-abliterated:4b ``` Then rebuild: `ollama create metatron-qwen -f Modelfile` ### 5. Set up MariaDB ```bash sudo systemctl start mariadb sudo systemctl enable mariadb mysql -u root ``` ```sql CREATE DATABASE metatron; CREATE USER 'metatron'@'localhost' IDENTIFIED BY '123'; GRANT ALL PRIVILEGES ON metatron.* TO 'metatron'@'localhost'; FLUSH PRIVILEGES; EXIT; ``` Create all tables: ```bash mysql -u metatron -p123 metatron < schema.sql ``` Or manually (paste from README schema block). The 5 tables: - `history` — one row per scan session (spine) - `vulnerabilities` — findings per session - `fixes` — remediation per vulnerability - `exploits_attempted` — exploit attempts per session - `summary` — raw scan + full AI analysis dump --- ## Running METATRON METATRON requires **two terminals**: **Terminal 1 — Load model into memory:** ```bash ollama run metatron-qwen # Wait for >>> prompt before proceeding ``` **Terminal 2 — Launch the assistant:** ```bash cd ~/METATRON source venv/bin/activate python metatron.py ``` ### Main Menu Flow ``` [1] New Scan → enter target IP/domain → select tools → AI analyzes → saved to DB [2] View History → browse past scans → view/edit/delete/export [3] Exit ``` ### New Scan — Tool Selection ``` [1] nmap [2] whois [3] whatweb [4] curl headers [5] dig DNS [6] nikto [a] Run all (except nikto) [n] Run all + nikto (slow, thorough) ``` ### Exporting Reports From **View History → select scan → export**: - `P