gemini-tool-orchestrator
Skill4 starsChanged 5 months agoMITView on GitHub
Natural-language orchestration of security tools through Gemini. Translates intent ("scan this scope for exposed admin panels") into safe, parameterized tool pipelines using nmap, masscan, naabu, httpx, nuclei, ffuf, gobuster, subfinder, amass, dnsx, katana, gau, semgrep, trivy, checkov, gitleaks, syft, grype, and custom scripts. Use when the user wants Gemini to drive a chain of CLI tools end to end with guardrails.
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Prefer read-only, low-rate, lab-confirmed pipelines first.
- Very specific: line 19
Run idempotently: write to ./runs/<utc>-<goal>/, dedupe inputs, and emit JSON Lines so later stages can stream-process.
- Distinctive: line 39
Never chain credential brute force, exploit delivery, or persistence steps.
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Gemini Tool Orchestrator
Authorization Boundary
- Require explicit scope: target list, exclusions, rate, time window, and written authorization reference before any active step.
- Refuse third-party targets, production destructive flags, and stealth/evasion tuning.
- Prefer read-only, low-rate, lab-confirmed pipelines first.
Orchestration Pattern
- Translate user intent into a goal: discovery, surface mapping, vulnerability triage, secrets review, SBOM, IaC review, or evidence collection.
- Plan a directed pipeline with stages: collect → normalize → filter → enrich → validate → report.
- For each stage, output: tool, exact command, why this flag, expected artifact path, runtime cap, and failure handling.
- Run idempotently: write to
./runs/<utc>-<goal>/, dedupe inputs, and emit JSON Lines so later stages can stream-process. - Gate active stages (nuclei, ffuf, fuzzers) on a
--confirm-scopeflag the user must pass.
Reference Pipelines
- Attack surface:
subfinder | dnsx | httpx | katana | nuclei -severity high,critical. - Web fuzz:
httpx → ffuf -w <wordlist> -mc 200,401,403 -fs <baseline>. - Code & supply chain:
semgrep --config auto,gitleaks detect,syft dir:. -o spdx-json | grype. - Cloud/IaC:
checkov -d .,trivy config .,tfsec .. - Container:
trivy image <ref>,grype <ref>,dockle <ref>.
Output Contract
plan.md: stages, commands, rationale, rollback.artifacts/: raw tool output, one file per stage.findings.jsonl: normalized{id, target, signal, severity, evidence, source_tool, confidence}.summary.md: top risks, next manual checks, false-positive notes.
Safety Rails
- Never chain credential brute force, exploit delivery, or persistence steps.
- Cap concurrency and request rate; default to single-threaded when scope is ambiguous.
- Strip secrets from logs before writing to disk.
Other versions1 project uses a version of this.
Word for word · 1
- Garyson26/Trident-SecOps-Skills★ 1100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository45 other files it gives its agents.
- ai-redteamSkill
- api-security-automationSkill
- assembly-programmingSkill
- bug-bounty-workflowSkill
- claude-mythos-emulationSkill
- cloud-security-automationSkill
- cybersecurity-partnerSkill
- detection-engineeringSkill
- devsecopsSkill
- exploit-developmentSkill
- forensics-triageSkill
- go-programmingSkill
- kubernetes-securitySkill
- malware-reverse-engineeringSkill
- multilingualSkill
- offensive-securitySkill
- prompt-enhancementSkill
- python-programmingSkill
- ai-redteamSkill
- api-security-automationSkill
- assembly-programmingSkill
- bug-bounty-workflowSkill
- claude-mythos-emulationSkill
- cloud-security-automationSkill
- cybersecurity-partnerSkill
- detection-engineeringSkill
- devsecopsSkill
- exploit-developmentSkill
- forensics-triageSkill
- gemini-tool-orchestratorSkill
- go-programmingSkill
- kubernetes-securitySkill
- malware-reverse-engineeringSkill
- multilingualSkill
- offensive-securitySkill
- osint-recon-automationSkill
- prompt-enhancementSkill
- purple-team-automationSkill
- python-programmingSkill
- smart-contract-auditSkill
- soc-operationsSkill
- threat-intel-fusionSkill
- smart-contract-auditSkill
- soc-operationsSkill
- threat-intel-fusionSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.