Add Jenkins CLI community plugin entry

[avivsinai]

Summary\n- add Jenkins CLI to Community Plugins > Tools & Integrations\n- keep the entry alphabetical and one-line per the contribution guidelines\n\n## Entry\n- Jenkins CLI - GitHub CLI-style interface for Jenkins controllers with jobs, pipelines, runs, logs, artifacts, credentials, and nodes.\n\n## Validation\n- confirmed the repository is public and includes a valid .codex-plugin/plugin.json manifest\n- verified the README insertion remains alphabetical within the section\n

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

The entry is correctly placed in alphabetical order between "Context Pack" and "KiCad Happy", follows the established list format (- [Name](url) - Description.), and the description is concise.

Files Reviewed (1 file)

• README.md - Single line addition, no issues

---

_{Reviewed by mimo-v2-pro-20260318 · 70,148 tokens}

[gemini-code-assist]

Code Review

This pull request adds the Jenkins CLI plugin to the third-party plugins list in the README. Feedback indicates that the plugins.json manifest is now out of sync and needs to be updated by running the provided generation script to ensure consistency.

[gemini-code-assist]

The plugins.json file is currently out of sync with the new entry in README.md. According to the documentation in scripts/generate_plugins_json.py, that script should be run after any change to the plugin list to regenerate the JSON manifest, update the total count, and refresh the timestamp. Please run the script and include the updated plugins.json in this pull request to ensure the machine-readable registry remains consistent.

[kantorcodes]

🎉 Your plugin has been merged and is now listed in the HOL Registry!

Claim your plugin

As the author, you can verify ownership of your plugin to unlock:

• Owner-verified badge on your plugin's registry listing
• Trust score visibility and analytics for your plugin
• Direct claim link to share with your community
• Dashboard access at hol.org/guard/plugins to track installs, trust, and engagement

How to claim

1. Visit hol.org/guard/plugins
2. Find your plugin and click "Verify ownership"
3. Sign in with GitHub — we only request read:user, user:email, and read:org (no write access to your repos)
4. We verify you own the repository, and your plugin gets the ✅ owner-verified badge

The whole process takes under 30 seconds. No need to add any secrets or tokens to your repo — verification is done entirely through GitHub OAuth.

If you have any questions, feel free to ask here or reach out at support@hol.org.