ingpoc/add-to-global-trigger
add-to-global-trigger/SKILL.md
Route proposed additions to the global Codex control plane by deciding whether a request belongs in `~/.codex/AGENTS.md`, a global workflow or reference doc under `~/.codex/docs`, `~/.codex/bin/workflow.py`, or an enforceable non-prose surface. Use when asked to "add this to global AGENTS", "promote this workflow to global", "add a new global trigger", or decide whether something should be a trigger, workflow, reference, hook, lint rule, or runtime guard.
$ install --global
skillsauthnpx skillsauth add ingpoc/skills add-to-global-triggerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 4, 2026, 9:25 AM210.7s3 files scanned
SKILL.md
- name:
- add-to-global-trigger
- description:
- Route proposed additions to the global Codex control plane by deciding whether a request belongs in `~/.codex/AGENTS.md`, a global workflow or reference doc under `~/.codex/docs`, `~/.codex/bin/workflow.py`, or an enforceable non-prose surface. Use when asked to "add this to global AGENTS", "promote this workflow to global", "add a new global trigger", or decide whether something should be a trigger, workflow, reference, hook, lint rule, or runtime guard.
Add To Global Trigger
Overview
Use this skill to add or refuse additions to the global Codex trigger layer without blurring surface ownership. Decide the owner surface first, then edit only the surfaces the request actually needs.
Global scope only:
~/.codex/AGENTS.md~/.codex/docs/~/.codex/bin/workflow.py
Do not use this skill for repo-local AGENTS.md work.
Decision Order
- Run
workflow summary placement. - Search existing global docs, skills, and trigger lines before adding anything.
- Classify the request into exactly one primary owner:
AGENTS.mdfor a short, stable routing rule that points to an existing durable target.docs/workflows/for a runtime multi-step process.docs/references/ordocs/quality-gate/for authoring guidance, checklists, or validation rules.- hooks, lint, deny rules, or runtime config when the behavior is deterministic and enforceable.
skills/when the request is a reusable method with judgment.
- Author the durable target before adding the trigger that points to it.
- Edit
~/.codex/AGENTS.mdlast.
If the request is longer than three short lines of stable instruction, do not put the full content in AGENTS.md. Create or update the owning surface and add only a compact trigger.
Search Before Writing
Run targeted retrieval before editing:
workflow list
workflow search "<topic>"
rg -n "<topic>|<candidate-name>" ~/.codex/AGENTS.md ~/.codex/docs ~/.codex/skills -g '*.md'
Collapse duplicates instead of creating parallel guidance. If an existing doc or skill already owns the concept, update that surface rather than adding a new one.
Surface Rules
Trigger Only
Choose this path only when all of the following are true:
- the durable target already exists
- the rule is stable and short
- the trigger can route through
workflow summary <doc>or another existing surface - no new enforcement or new method is required
Before editing ~/.codex/AGENTS.md, run:
workflow summary agentmd-quality-gate
New Workflow or Reference Doc
Choose a new doc when the trigger needs a durable target.
- Use a workflow doc for runtime execution steps.
- Use a reference or quality-gate doc for authoring guidance or checklists.
Before creating the doc, run:
workflow summary workflow-doc-creation
Do not describe global doc creation as a reindex task. Global docs are discovered by filesystem scan.
Workflow CLI Alias Support
Edit ~/.codex/bin/workflow.py only when the new doc needs first-class short-name support through workflow summary <name>, workflow read <name>, or other alias-based routing.
Before changing workflow.py, run:
workflow summary workflow-cli-quality-gate
Measure before and after for the command path you changed. Treat alias support as a CLI surface change, not just a doc change.
Enforced Instead of Prose
Do not add prose when the request is really about blocking or mechanically steering behavior. Prefer:
rumdlfor recurring Markdown misuserufffor recurring Python misuse- hooks or deny rules for unsafe actions
- runtime config for hard restrictions
If you route to enforcement, explain briefly why the request should not become a global trigger or doc.
Authoring Order
Follow this order exactly:
workflow summary placement- search existing global surfaces
- if creating a doc,
workflow summary workflow-doc-creationand author the doc - if alias support is needed,
workflow summary workflow-cli-quality-gateand update~/.codex/bin/workflow.py - if editing
AGENTS.md,workflow summary agentmd-quality-gate - add or update the global trigger line in
~/.codex/AGENTS.md - run validation for every touched surface
Use the exact command sequences in surface-matrix.md.
Validation
Always validate the surfaces you touched.
~/.codex/AGENTS.mdchanged:- verify the line is concise, bounded, and points to an existing target
- global doc created or edited:
workflow registryworkflow lint
~/.codex/bin/workflow.pychanged:workflow lintworkflow lint --fullpython3 -m unittest discover -s /Users/gurusharan/.codex/tests -p 'test_workflow_cli_regression.py'- manual check that
workflow summary <alias>works
If workflow registry shows unrelated pre-existing drift, report it but do not fix it unless the requested change depends on it.
Refusal Cases
Refuse or reroute when:
- the request is repo-local rather than global
- the content is session-specific
- the content is derivable from code or git history instead of deserving a durable doc
- the request wants prose where enforcement is the right owner
- the new trigger would duplicate an existing global trigger or doc
Related Skills
ingpoc/cloudflare-deploy
devops
VerifiedTrustedCommunity
Deploy applications and infrastructure to Cloudflare using Workers, Pages, and related platform services. Use when the user asks to deploy, host, publish, or set up a project on Cloudflare.
7SKILL.mdUpdated Jun 4, 2026
ingpoc/cli-for-agents
tools
VerifiedTrustedCommunity
Design or review CLIs so both coding agents and humans can use them reliably: dual-audience output, non-interactive paths, layered help, machine-readable data, predictable flags, safe mutations, and actionable errors. Use when building a CLI, adding commands, writing --help, or when the user mentions agents, terminals, automation-friendly CLIs, JSON output, or headless usage.
7SKILL.mdUpdated Jun 4, 2026
ingpoc/cli-creator
tools
VerifiedTrustedCommunity
Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script. Use when the user wants Codex to create a command-line tool that can run from any repo, expose composable read/write commands, return stable JSON, manage auth, and pair with a companion skill.
7SKILL.mdUpdated Jun 4, 2026
ingpoc/claude-glm-agent
development
VerifiedTrustedCommunity
Use when configuring apps to use z.ai GLM 4.7 proxy instead of standard Anthropic API. Works with any frontend (Next.js, Vite) or backend (Python, Node.js) framework.
7SKILL.mdUpdated Jun 4, 2026