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/ahmed-lakosha/odoo-pluginsWrote 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/ahmed-lakosha/odoo-plugins/odoo-docker-plugin)<a href="https://agentmods.dev/plugins/ahmed-lakosha/odoo-plugins/odoo-docker-plugin"><img src="https://agentmods.dev/badge/plugins/ahmed-lakosha/odoo-plugins/odoo-docker-plugin/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/ahmed-lakosha/odoo-plugins/odoo-docker-plugin"><img src="https://agentmods.dev/badge/plugins/ahmed-lakosha/odoo-plugins/odoo-docker-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
odoo-docker-plugin 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.
What it actually says
{
"name": "odoo-docker",
"version": "2.1.0",
"description": "Docker infrastructure manager for Odoo - production deployment with nginx, CI/CD pipelines, performance tuning, multi-version image management, container debugging, and centralized workspace orchestration for Odoo 14-19 Enterprise.",
"author": {
"name": "TaqaTechno",
"email": "[email protected]",
"url": "https://github.com/taqat-techno"
},
"homepage": "https://github.com/taqat-techno/plugins",
"repository": "https://github.com/taqat-techno/plugins",
"license": "MIT",
"keywords": [
"odoo",
"docker",
"nginx",
"deployment",
"infrastructure",
"ci-cd",
"performance",
"docker-compose",
"production",
"debugging",
"multi-version"
],
"skills": [
"./odoo-docker"
],
"commands": [
"./commands"
],
"hooks": "./hooks/hooks.json"
}
What it installs
The manifest is a name and a version. 1 skill, 1 command, 1 hook travel with it, and installing the plugin installs all of them — 628 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 · 34 lines scan A c9a06dab08c6
odoo-docker-plugin is a plugin published in the GitHub repository ahmed-lakosha/odoo-plugins (76 stars, last pushed 6mo ago), licensed MIT. 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
deploy-pilot
Deployment automation with Dockerfile generation, CI/CD pipelines, and infrastructure as code.
clouddrove
Team DevOps review and scaffolding skills: Terraform (source and plan), Kubernetes/Helm, Docker, GitHub Actions, GitLab CI, Argo CD/Flux, AWS FinOps, OWASP and application security, observability, incident runbooks, deployment gating, and ADRs. Findings carry shared auditkit rule IDs.
deployment-engineer
Use this agent when setting up CI/CD pipelines, configuring Docker containers, deploying applications to cloud platforms, setting up Kubernetes clusters, implementing infrastructure as code, or automating deployment workflows. Examples: Context: User is setting up a new project and needs deployment automation.
portal-skills
Platform engineering and security skills: GitLab CI/CD + Helm chart generation for Kubernetes, data-driven pod rightsizing from Prometheus, a proactive secure-coding baseline, and a deep OWASP reference (Top 10:2025, LLM Top 10, Agentic AI).
engineering-skills
Software engineering workflow skills: code review, Git workflow, API design, Docker Compose generation, database schema design, CI/CD pipelines, GitLab CI with Kiro CLI headless AI jobs and MCP integration, Terraform modules, Python project setup, test generation, and Kiro project setup.
ci-incident-medic
Triages failing GitHub Actions runs, hardens Dockerfiles, pre-flights Kubernetes manifests before they reach the cluster, and drafts blameless postmortems from incident evidence.