Agent skill · Data & Analytics

verify-agent-action

Review a proposed AI-agent action or human-approval packet before execution. Use when an agent wants to run a consequential tool, command, deployment, message, purchase, credential operation, or data mutation; when checking whether approval still matches the exact action; or when auditing action evidence for forged results, parameter swaps, replay, correlated reviewers, missing evidence, expiry, or stale monitoring. Produce an evidence-based review only—never execute or authorize the action.

GitHub68,948★ · +463/wk · 2 repos on radarProfile →
copilotMIT
Install
npx skills add github/awesome-copilot --skill verify-agent-action --agent copilot

Same command for any agent — swap --agent for claude-code, codex, cursor.

Facts
Files in the skill folder: 1
SKILL.md size: 8 KB
Bundled scripts: none
Path: skills/verify-agent-action/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 37,432 · +281 this week
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Verify Agent Action Treat a plausible approval screen as a claim, not proof. Verify the complete decision path before a human or an external enforcement point decides whether to act. ## Preserve the safety boundary - Never execute, approve, sign, send, purchase, deploy, or mutate anything. - Never convert this review into execution authority. - Never infer missing evidence, identities, timestamps, or parameters. - Treat a valid schema, checksum, or signature as insufficient by itself. - Treat signatures as evidence of attribution and integrity, not factual truth. - Keep supporting and refuting evidence separate; do not average conflict away. - Fail closed on a material mismatch. Use `INCONCLUSIVE` when required evidence is unavailable. Set this field in every final result: ```json {"execution_authorized": false} ``` ## Collect the review packet Request only the artifacts needed for the review: 1. The original user or system request. 2. The exact proposed action: - operation or tool name - target resource - complete parameters - filesystem and network scope - maximum execution count - not-before and expiry times 3. The assessment that claims the action is justified. 4. The source

What's inside
Steps it walks through
  1. Preserve the safety boundary
  2. Collect the review packet
  3. Build the exact action identity
  4. Run the six controls
  5. 1. Recompute the assessment
  6. 2. Match the exact approved action
  7. 3. Reject replay and identity ambiguity
  8. 4. Test reviewer independence
  9. 5. Preserve evidence and contradiction
  10. 6. Verify lifecycle and monitoring
  11. Challenge convenient conclusions
  12. Determine the review result
  13. Report in this format
More from awesome-copilot
All skills →
About this skill
What does the verify-agent-action skill do?

Review a proposed AI-agent action or human-approval packet before execution. Use when an agent wants to run a consequential tool, command, deployment, message, purchase, credential operation, or data mutation; when checking whether approval still matches the exact action; or when auditing action evidence for forged results, parameter swaps, replay, correlated reviewers, missing evidence, expiry, or stale monitoring. Produce an evidence-based review only—never execute or authorize the action.

How do I install it?

Run `npx skills add github/awesome-copilot --skill verify-agent-action --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going