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.
npx skills add thePM001/AEP-agent-element-protocol --skill agentsh-policy-editgit clone --depth 1 https://github.com/thePM001/AEP-agent-element-protocolWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/thepm001/aep-agent-element-protocol/agentsh-policy-edit)<a href="https://agentmods.dev/skills/thepm001/aep-agent-element-protocol/agentsh-policy-edit"><img src="https://agentmods.dev/badge/skills/thepm001/aep-agent-element-protocol/agentsh-policy-edit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/thepm001/aep-agent-element-protocol/agentsh-policy-edit"><img src="https://agentmods.dev/badge/skills/thepm001/aep-agent-element-protocol/agentsh-policy-edit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00046 | $0.01567 |
| Opus 5 | $0.00023 | $0.00783 |
| Sonnet 5 | $0.00009 | $0.00313 |
| Haiku 4.5 | $0.00005 | $0.00157 |
Grade A, and why
aep-caw-policy-edit 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 9d ago.
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.
This is a copy
94% identical to agentsh-policy-edit — 42 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edit AepCaw Policy
Overview
Make targeted edits to existing AepCaw security policies - add, remove or update rules and declarations. Understands most-specific collect-all policy categories plus the separate Postgres-family database rule semantics.
When to Use
- User asks to add/remove/update a policy rule ("allow stripe.com", "block file deletes")
- User asks to change declared HTTP API access (
http_services,providers) - User asks to change Postgres-family DB access (
db_services,database_rules,database_connection_rules,policies.db) - User wants to change resource limits or audit settings
- User mentions modifying an existing policy
- NOT for creating new policies from scratch (use aep-caw-policy-create)
Flow
-
Locate & read the policy
- Check
config.yml/config.yamlforpolicies.dir - If not found, look for
configs/policies/directory - Fall back to asking the user
- If multiple policies exist, list them and ask which one to edit
- Read the full YAML into context
- Check
-
Understand the intent Map the user's request to:
- Rule category - file_rules, network_rules, command_rules, unix_socket_rules, registry_rules, signal_rules, dns_redirects, connect_redirects, http_services, providers, db_services, database_rules, database_connection_rules, policies.db, resource_limits, env_policy, audit, mcp_rules, package_rules, process_contexts, process_identities, env_inject, transparent_commands
- Operation - add a new rule, remove an existing rule, or modify an existing rule
- Insertion position - where in the rule order (for new rules)
-
Determine insertion position (for new rules) First-match-wins means ordering matters:
- Place deny rules before any broader matching rule regardless of its decision - any non-deny rule (
allow,approve,redirect,audit,absorb,soft_delete) that matches first will shadow the deny - Place allow rules before the default-deny catch-all at the end
- Place more specific rules before less specific ones
- When in doubt: deny rules go before the first non-deny rule in that category; allow rules go before the default-deny
- Do not apply a listing-order shortcut to
database_rulesordatabase_connection_rules; see DB rules below.
- Place deny rules before any broader matching rule regardless of its decision - any non-deny rule (
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.
- 9d ago First seen · 103 lines · 46 tokens per session scan A eb965bf4494a
aep-caw-policy-edit is a skill published in the GitHub repository thePM001/AEP-agent-element-protocol (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,567 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to agentsh-policy-edit, differing in 42 lines, and is treated as a copy.
Other skills, from other repositories
design-taste-frontend
Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.
image-to-code
Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards…
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.
minimalist-ui
Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.
widgets
Render rich HTML inline via tags with theme-aware styling. Load when emitting an mcwidget so the iframe inherits the dashboard theme instead of clashing with light / dark / custom palettes.
web-verify
Look at your OWN front-end change before claiming it works -- navigate the loopback URL of a dev server or pod you started, screenshot the surface you changed, read the image to judge it, and embed it in chat. Three capture backends: playwright-cli (the session the dashboard Browser panel shows), the agent-browser CLI…