Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/manutej/luxor-claude-marketplaceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/plugins/manutej/luxor-claude-marketplace/luxor-data-engineering)<a href="https://agentmods.dev/plugins/manutej/luxor-claude-marketplace/luxor-data-engineering"><img src="https://agentmods.dev/badge/plugins/manutej/luxor-claude-marketplace/luxor-data-engineering/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/manutej/luxor-claude-marketplace/luxor-data-engineering"><img src="https://agentmods.dev/badge/plugins/manutej/luxor-claude-marketplace/luxor-data-engineering.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
LUXOR Data Engineering scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What it installs
The manifest is a name and a version. 5 skills travel with it, and installing the plugin installs all of them — 165 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 65 lines scan A 74811e96e525
LUXOR Data Engineering is a plugin published in the GitHub repository manutej/luxor-claude-marketplace (62 stars, last pushed 4mo ago), with no licence file. Its token cost is not measured: this kind of file is read by the harness, not the model. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other plugins, from other repositories
devops-tools
DevOps automation: ClickHouse, Doppler, MLflow, Cloudflare Workers, pueue orchestration, notifications, session recovery, LLM session debriefs.
minimax
MiniMax M-series production wiring: OpenAI-compat quirks, hybrid prompt caching, Tier F quant agentic stack, model-upgrade detection. Distilled from a 41-iteration M2.7-highspeed exploration campaign.
ai-toolkit
Skills for Deep Learning (Keras 3), Reinforcement Learning (Python & C++), Claude Prompt Optimization, x402 Web3 Payments, and OpenClaw Setup.
prompt-refiner
Hybrid prompt linter — deterministic Node detector for 18 of 20 rules plus an LLM model layer for PR003, PR009, and semantic cases of PR002, PR005, and PR010. Lint, don't rewrite. Markdown or JSON output, suppression comments, baseline mode, conformance corpus (25 cases), CI recipes. Never imposes a framework, never…
uitkit-ai-engineering
Claude API, agent construction, RAG, LangGraph, CrewAI, MCP server building, prompt caching, LLM eval, and AI-native development patterns.
pr-provenance-stamp
Embeds a reviewer-facing provenance receipt into your PR body when Claude runs gh pr create (or glab mr create). A PostToolUse hook (async, zero added latency) records a per-session ledger: tool calls, agent-authored lines, and every test/typecheck command with its real exit code; a PreToolUse (Bash) hook then rewr.