[PR #78] [MERGED] Add Temodar Agent to CMS section #481

New Issue

GiteaMirror · 2026-05-07T04:49:58-05:00

GiteaMirror commented

2026-05-07 04:49:58 -05:00

📋 Pull Request Information

Original PR: https://github.com/vavkamil/awesome-bugbounty-tools/pull/78
Author: @xeloxa
Created: 2/6/2026
Status: ✅ Merged
Merged: 4/8/2026
Merged by: @vavkamil

Base: main ← Head: main

📝 Commits (1)

11b7aba Add Temodar Agent to CMS section

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

Hello! I’d like to update this submission for Temodar Agent (formerly WP-Hunter) and request its inclusion in the CMS section.

Since the original PR, the project has evolved significantly beyond a simple WordPress reconnaissance tool.

Temodar Agent is an AI-powered WordPress plugin and theme security analysis platform built for security researchers, product security teams, auditors, and defenders. It combines WordPress target triage, Semgrep-powered static analysis, and AI-assisted investigation workflows in a local-first Docker application.

What changed since WP-Hunter

Project renamed: WP-Hunter → Temodar Agent
Expanded from a focused reconnaissance/SAST tool into a broader security analysis platform
Added AI agent-based investigation workflows
Added multi-provider LLM orchestration
Improved plugin and theme analysis
Added more structured Semgrep-based triage and review workflows

Key capabilities

WordPress plugin and theme scanning
Risk-based prioritization for target triage
Semgrep-powered static analysis
AI-assisted investigation threads
Multi-provider AI support
Local-first workflow with historical review and persisted results

Repository:

https://github.com/xeloxa/temodar-agent

I know the project previously did not meet the list criteria, but I wanted to resubmit it now that the scope, maturity, and overall value have grown considerably.

If needed, I’d be happy to further refine the description to better match the list’s inclusion standards.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/vavkamil/awesome-bugbounty-tools/pull/78 **Author:** [@xeloxa](https://github.com/xeloxa) **Created:** 2/6/2026 **Status:** ✅ Merged **Merged:** 4/8/2026 **Merged by:** [@vavkamil](https://github.com/vavkamil) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`11b7aba`](https://github.com/vavkamil/awesome-bugbounty-tools/commit/11b7aba4dbd14e4166fcb29a3307072760f27f07) Add Temodar Agent to CMS section ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description Hello! I’d like to update this submission for **Temodar Agent** (formerly **WP-Hunter**) and request its inclusion in the CMS section. Since the original PR, the project has evolved significantly beyond a simple WordPress reconnaissance tool. **Temodar Agent** is an AI-powered WordPress plugin and theme security analysis platform built for security researchers, product security teams, auditors, and defenders. It combines WordPress target triage, Semgrep-powered static analysis, and AI-assisted investigation workflows in a local-first Docker application. ### What changed since WP-Hunter - **Project renamed:** WP-Hunter → Temodar Agent - Expanded from a focused reconnaissance/SAST tool into a broader **security analysis platform** - Added **AI agent-based investigation workflows** - Added **multi-provider LLM orchestration** - Improved **plugin and theme analysis** - Added more structured **Semgrep-based triage and review workflows** ### Key capabilities - WordPress **plugin and theme** scanning - Risk-based prioritization for target triage - **Semgrep-powered** static analysis - **AI-assisted investigation threads** - **Multi-provider AI support** - Local-first workflow with historical review and persisted results Repository: - https://github.com/xeloxa/temodar-agent I know the project previously did not meet the list criteria, but I wanted to resubmit it now that the scope, maturity, and overall value have grown considerably. If needed, I’d be happy to further refine the description to better match the list’s inclusion standards. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-05-07 04:49:58 -05:00

GiteaMirror closed this issue

2026-05-07 04:49:58 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-bugbounty-tools#481