Skip to content

ForgeGuard v1.2.0 — Automatic AGENTS.md Integration

Choose a tag to compare

View all tags
@github-actions github-actions released this 19 Aug 11:52
v1.2.0
b03aae4

ForgeGuard v1.2.0 — Automatic AGENTS.md Integration

ForgeGuard v1.2.0 connects the installed Agent Skill directly to Codex repository instructions.

The main change is simple: installing ForgeGuard no longer only copies engineering-guardrails into a skills directory. For Codex installations, the CLI now also adds a small managed ForgeGuard activation block to the active AGENTS.md instruction file so repository work consistently discovers and applies the skill.

Highlights

Automatic Codex instruction integration

Running:

npx --yes github:GendByteMaster/ForgeGuard install

now installs the skill and, when Codex is among the selected clients, adds a ForgeGuard-managed block to the active repository instructions.

The managed block tells Codex to load engineering-guardrails before implementation, bug fixes, refactors, migrations, security-sensitive work, production changes, or commit preparation.

It also explicitly activates ForgeGuard's:

  • Risk Gate;
  • explicit Subagent approval gate;
  • repository-local instruction preservation;
  • safe fallback behavior when the skill cannot be loaded.

Idempotent AGENTS.md management

ForgeGuard uses explicit managed markers:

<!-- forgeguard:managed-start -->
...
<!-- forgeguard:managed-end -->

This gives the CLI ownership of only its own section.

Repeated installs update the existing managed block instead of appending duplicates. Existing user instructions outside the block remain untouched.

AGENTS.override.md awareness

When a non-empty AGENTS.override.md exists in the active Codex instruction scope, ForgeGuard uses it instead of writing a competing block to AGENTS.md.

The CLI keeps the managed activation block in only the active instruction file to avoid conflicting ForgeGuard instructions.

Safe uninstall

forgeguard uninstall now removes both:

  • installed ForgeGuard skill directories for the selected clients;
  • the ForgeGuard-managed block from Codex instructions.

If an AGENTS.md file contains other project instructions, those instructions are preserved. If ForgeGuard created a file that contains nothing except the managed block, the empty file is removed during uninstall.

Status includes instruction linkage

forgeguard status now reports Codex instruction integration in addition to skill installation state.

Example output can distinguish:

installed codex+cursor: .../.agents/skills/engineering-guardrails (v1.2.0)
installed claude: .../.claude/skills/engineering-guardrails (v1.2.0)
linked    agents: .../AGENTS.md

Opt-out with --no-agents

Projects that want the skill installed without modifying Codex instructions can use:

forgeguard install --client codex --no-agents

This keeps AGENTS integration explicit and reversible rather than mandatory.

Global installation

For global Codex installation, ForgeGuard uses CODEX_HOME when configured and otherwise falls back to ~/.codex for the managed instruction file.

The skill itself continues to use the supported user-level Agent Skills directory.

Session reload requirement

Codex loads repository instructions when a session starts. After ForgeGuard changes AGENTS.md or AGENTS.override.md, start a new Codex session so the updated instructions are loaded.

The CLI prints this reminder after installation.

CI hardening

The CLI workflow was updated alongside v1.2.0:

  • Node 18, 20, and 22 run independently with matrix fail-fast: false;
  • expected versions are read dynamically from package.json instead of being hardcoded;
  • CI verifies skill installation and AGENTS integration;
  • repeated installation is tested for idempotency;
  • uninstall cleanup is verified;
  • npm pack --dry-run continues to validate the distributable npm artifact.

CLI

Project installation:

npx --yes github:GendByteMaster/ForgeGuard install

Status:

npx --yes github:GendByteMaster/ForgeGuard status

Uninstall:

npx --yes github:GendByteMaster/ForgeGuard uninstall

Codex only:

npx --yes github:GendByteMaster/ForgeGuard install --client codex

Global:

npx --yes github:GendByteMaster/ForgeGuard install --global

Skip AGENTS integration:

npx --yes github:GendByteMaster/ForgeGuard install --client codex --no-agents

Upgrade from v1.1.0

Re-run the installer with --force:

npx --yes github:GendByteMaster/ForgeGuard install --force

This refreshes the installed skill to v1.2.0 and adds or updates the managed Codex instruction block.

Then start a new Codex session.

Breaking changes

None.

The new AGENTS integration is automatically enabled when Codex is selected, but it is isolated to a managed block and can be disabled with --no-agents or completely removed with uninstall.

License

MIT.

Assets 2
Loading