Skip to content
Back to skills

Pre Execute Check

ASecurity

Check AxonFlow governance policy before executing commands, writing files, or modifying any state. Also scan file content for PII before writing. Use before any tool call that creates, modifies, or deletes data.

  • 3 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added September 12, 2026
ai-agentsgobashsqlgit

Works with

  • terminal
  • mcp

Security analysis

A100/100

Scanned September 12, 2026

npx -y skills add thedixitjain/the-mega-skill-library --skill pre-execute-check --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Pre Execute Check?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Pre Execute Check
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thedixitjain-pre-execute-check/badge)](https://www.skillsdirectory.com/skills/thedixitjain-pre-execute-check)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: pre-execute-check
description: "Check AxonFlow governance policy before executing commands, writing files, or modifying any state. Also scan file content for PII before writing. Use before any tool call that creates, modifies, or deletes data."
category: ai-agents-and-harness
source_repo: hashgraph-online/awesome-codex-plugins
source_path: "plugins/getaxonflow/axonflow-codex-plugin/skills/pre-execute-check/SKILL.md"
source_url: https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/getaxonflow/axonflow-codex-plugin/skills/pre-execute-check/SKILL.md
---


Before using tools that modify state (terminal commands, file writes, file edits, MCP operations):

**Step 1: Check policy**

Call the `check_policy` MCP tool with:
- `connector_type`: `codex.Bash` (for commands), `codex.Write` (for file writes), or the appropriate tool type
- `statement`: the command or content to check
- `operation`: `execute`

If the response shows `allowed: false`, do NOT proceed. Report the block reason to the user.

**Step 2: For file writes — also scan content for PII**

If you are writing a file and the content might contain sensitive data (names, SSNs, credit cards, emails, phone numbers, addresses, medical records, financial data), call the `check_output` MCP tool with:
- `connector_type`: `codex.Write`
- `message`: the content being written

If a `redacted_message` is returned, write the redacted version instead. If `allowed: false`, do not write the file.

These checks take 2-5ms and protect against dangerous commands, SQL injection, credential access, SSRF, path traversal, and PII exposure.

---

**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/getaxonflow/axonflow-codex-plugin/skills/pre-execute-check/SKILL.md`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.