Skip to content

Restore ArmorCodex entry in Community Plugins (lost during PR #115 reconcile)#189

Open
Harihara04sudhan wants to merge 4 commits into
hashgraph-online:mainfrom
Harihara04sudhan:restore-armorcodex
Open

Restore ArmorCodex entry in Community Plugins (lost during PR #115 reconcile)#189
Harihara04sudhan wants to merge 4 commits into
hashgraph-online:mainfrom
Harihara04sudhan:restore-armorcodex

Conversation

@Harihara04sudhan

Copy link
Copy Markdown

Summary

Restore the ArmorCodex entry under Community Plugins -> Tools & Integrations. It was originally added in PR #140 (merged 2026-05-20 14:45 UTC) but got accidentally dropped 5 minutes later when PR #115 (Add 10 pluginpool plugins, merged 14:50 UTC) was reconciled.

You can confirm by looking at commit bc06f70: its diff includes a single -- of the ArmorCodex line alongside the ++ adds for the 10 new plugins.

Current state

Artifact Status
plugins/armoriq/armorCodex/.codex-plugin/plugin.json present (from PR #140)
plugins/armoriq/armorCodex/assets/icon.png present (from PR #140)
README entry missing (this PR)
.agents/plugins/marketplace.json armorcodex entry derived from README, will sync after merge

What this PR does

One-line restore in README.md:

 - [Apple Productivity](https://github.com/matk0shub/apple-productivity-mcp) - Local Apple Calendar and Reminders tooling for macOS with Codex plugin adapters.
+- [ArmorCodex](https://github.com/armoriq/armorCodex) - Intent-based security for Codex with MCP plan registration, policy gating, CSRG cryptographic proofs, and audit logging on Bash and apply_patch.
 - [AxonFlow](https://github.com/getaxonflow/axonflow-codex-plugin) - Runtime governance for Codex with policy enforcement on terminal commands, advisory checks for non-terminal tools via skills, PII/secret detection, and compliance-grade audit trails. Self-hosted via Docker.

Identical to the line PR #140 originally added. Inserted in the alphabetical slot between Apple Productivity and AxonFlow.

After merge

Once your existing "chore: sync marketplace artifacts with README" automation runs, ArmorCodex will appear in plugins.json and .agents/plugins/marketplace.json, and the codex plugin marketplace add flow will surface it.

Repo: https://github.com/armoriq/armorCodex

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds the ArmorCodex plugin to the list of third-party plugins in README.md. The review feedback suggests enclosing 'bash' and 'apply_patch' in backticks to maintain formatting consistency and prevent markdown parsing issues.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread README.md Outdated
- [Agentgram](https://github.com/jerryfane/agentgram) - Send explicit Telegram messages from Codex and local AI agents through a Telegram bot token and chat id.
- [Aient](https://github.com/haf/aient-codex-plugin) - AI operations plugin for Codex that connects production telemetry, problem lifecycle context, and remediation workflows through Aient's MCP server.
- [Apple Productivity](https://github.com/matk0shub/apple-productivity-mcp) - Local Apple Calendar and Reminders tooling for macOS with Codex plugin adapters.
- [ArmorCodex](https://github.com/armoriq/armorCodex) - Intent-based security for Codex with MCP plan registration, policy gating, CSRG cryptographic proofs, and audit logging on Bash and apply_patch.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

To maintain consistency with other entries in this document (such as rg, grep, and git blame), and to ensure that the underscore in apply_patch is not misinterpreted by markdown parsers, it is recommended to enclose bash (preferably lowercase) and apply_patch in backticks.\n\nFor example:\n- [ArmorCodex](https://github.com/armoriq/armorCodex) - Intent-based security for Codex with MCP plan registration, policy gating, CSRG cryptographic proofs, and audit logging on bashandapply_patch.

@internet-dot

Copy link
Copy Markdown
Collaborator

This PR only adds a README entry. For this bundle-required repo, a complete submission needs the full plugin bundle under plugins/armoriq/armorCodex/ plus entries in plugins.json and .agents/plugins/marketplace.json.\n\nIf the entry was lost during a prior merge, please resubmit with the complete bundle. See CONTRIBUTING.md.

@internet-dot

Copy link
Copy Markdown
Collaborator

Before this PR can be merged, your plugin repo needs the HOL AI Plugin Scanner running in CI. This is a mandatory requirement for all submissions.

Add this workflow to your plugin repo at .github/workflows/hol-plugin-scanner.yml:

name: HOL Plugin Scanner

on:
  push:
    branches: [main, master]
  pull_request:
    branches: [main, master]

permissions:
  contents: read
  security-events: write

jobs:
  scan:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683 # v4.2.2
      - name: HOL Plugin Scanner
        uses: hashgraph-online/ai-plugin-scanner-action@v1
        with:
          plugin_dir: "."
          mode: scan
          min_score: 80
          fail_on_severity: high
          format: sarif
          upload_sarif: true

Also run the scanner locally and include the score in your PR description:

pipx install plugin-scanner
plugin-scanner scan . --format text

Your plugin needs a score of 80/130 or higher with no critical or high severity findings. Link the CI run or paste the score in this PR description.

See the full guide: SCANNER_GUIDE.md

Additional issues:
This PR only restores a README line. You need to provide a full plugin bundle under plugins/armoriq/armorCodex/.

The ArmorCodex entry was added in PR hashgraph-online#140 (merged 2026-05-20 14:45 UTC)
but accidentally dropped 5 minutes later when PR hashgraph-online#115 (Add 10 pluginpool
plugins, merged 14:50 UTC) was reconciled. The plugin bundle at
plugins/armoriq/armorCodex/ remained intact, so the registry has the
plugin but README and downstream marketplace artifacts don't list it.

Restoring the README entry in its alphabetical slot between Apple
Productivity and AxonFlow. Plugin folder + plugin.json are already in
the repo from PR hashgraph-online#140; no other changes needed.

Repo: https://github.com/armoriq/armorCodex
Plugin bundle in this repo: plugins/armoriq/armorCodex/
Per gemini-code-assist review on this PR — keeps formatting consistent
with other entries (rg, grep, git blame) and prevents markdown parser
ambiguity around the underscore in apply_patch.
…ess Skills

Per the upstream alphabetical CI check (check-alphabetical.py). Pre-existing
ordering issue surfaced by the rebase, not caused by this PR — fixing here
since the check is required to pass.
Per @internet-dot's review comment requesting the full plugin bundle
(not just the README entry). This commit adds the complete ArmorCodex
plugin source tree, mirrored from armoriq/armorCodex@main:

- README.md, LICENSE, SECURITY.md
- .codexignore, .plugin-scanner.toml
- hooks/hooks.json (8 hook events declared)
- scripts/bootstrap.mjs, scripts/hook-router.mjs, scripts/policy-mcp.mjs
- scripts/lib/ (13 lib modules: engine, intent, policy, audit-wal, etc.)
- .agents/plugins/marketplace.json (per-plugin marketplace metadata,
  follows AgiFlow reference shape — name "armoriq", plugin name
  "armorcodex", category "Tools & Integrations", source URL pointing
  at the canonical github.com/armoriq/armorCodex repo)

Excluded from the bundle:
- node_modules/ (installed at runtime via package-lock.json)
- tests/ (moved out of the plugin distribution dir per scanner
  compliance; lives at the repo root in the source repo now)

Refs hashgraph-online#189
@Harihara04sudhan

Copy link
Copy Markdown
Author

@internet-dot — all asks addressed. Single summary:

What's now in the PR

Ask Status
Complete plugin bundle at plugins/armoriq/armorCodex/ ✅ 25 files: .codex-plugin/plugin.json, .codex/, .mcp.json, hooks/hooks.json (8 events), scripts/ (bootstrap + hook-router + policy-mcp + 13 lib modules), README.md, LICENSE, SECURITY.md, .codexignore, assets/armoriq-logo.png
Per-plugin .agents/plugins/marketplace.json ✅ Added (owner armoriq, plugin armorcodex, category Tools & Integrations, source URL https://github.com/armoriq/armorCodex.git, follows AgiFlow shape)
HOL Plugin Scanner workflow in our plugin repo ✅ Live on armoriq/armorCodex main, CI run 27229800929 green, score 92/100, 0 high/critical
Alphabetical Order Check ✅ Passing on this PR
Gemini bot suggestion (backticks on bash / apply_patch) ✅ Applied

What's excluded from the bundle (intentionally)

  • node_modules/ — resolved at runtime from package-lock.json
  • tests/ — moved out of the plugin distribution dir per scanner compliance; lives at repo root in the source repo

On the repo-wide HOL Plugin Scanner — Lint check

It is failing on this PR but the failure is repo-wide (failing identically on #202, #204, every open PR since the workflow was made mandatory in #199). I ran the lint locally against current main:

  • Total findings: 1333
  • HIGH findings: 139
  • HIGH findings referencing plugins/armoriq/armorCodex/: 0

The HIGH findings come from skills/sealos-deploy/scripts/*.mjs, skills-codex/standards/references/*.md, archcore.ai, agentops install scripts, and 5 in the repo's own README.md. None are introduced by this PR (which adds 1 README line + the standard bundle).

Standard fix for this scenario is --baseline mode: baseline the existing 139 highs against main so only NEW findings from a PR fail. Happy to send a follow-up PR with that baseline if it'd help.

Ready for re-review whenever you have a moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants