policy

A command for viewing or changing Workflow authorization policies. These policies control modes such as automatic approval, planning, manual approval, and full access.

In plain words
What is it for?
Use it to show the current policy or set a user-level policy or project-level .workflow-policy file.
Why use it?
It makes the active permission mode and its source visible before changes are made. Changes require confirmation and cannot use a project file to raise user permissions to full access.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/go1c/workflow-plugin/policy
Clone the repo
git clone --depth 1 https://github.com/Go1c/workflow-plugin
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 124 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.00124
Opus 5 $0.00008 $0.00062
Sonnet 5 $0.00003 $0.00025
Haiku 4.5 $0.00002 $0.00012

Measured yesterday against content hash d0caad216dd4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

policy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/policy.md · 12 lines

What it actually says

调起 workflow-ops 技能并读取 permission-modes.mdshow 只显示当前生效模式、来源和项目覆盖;set 只修改用户级 policy 或项目 .workflow-policy, 写入前展示目标文件与新旧值并取得明确确认。项目策略不得把用户级权限提升到 full,未知值停止。

操作:

$ARGUMENTS

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 12 lines · 16 tokens per session scan A d0caad216dd4

Subscribe to this mod's changes

policy is a command published in the GitHub repository Go1c/workflow-plugin (2 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 124 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.