Borrowing it
Nothing to install: this file belongs to safedep/gryph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/safedep/gryph/main/.claude/skills/gryph-policy-authoring/SKILL.mdgit clone --depth 1 https://github.com/safedep/gryphWrote 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/safedep/gryph/gryph-policy-authoring)<a href="https://agentmods.dev/skills/safedep/gryph/gryph-policy-authoring"><img src="https://agentmods.dev/badge/skills/safedep/gryph/gryph-policy-authoring/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/safedep/gryph/gryph-policy-authoring"><img src="https://agentmods.dev/badge/skills/safedep/gryph/gryph-policy-authoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 84 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 84 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00200 | $0.01825 |
| Opus 5 | $0.00100 | $0.00912 |
| Sonnet 5 | $0.00040 | $0.00365 |
| Haiku 4.5 | $0.00020 | $0.00183 |
Grade B, and why
gryph-policy-authoring scanned grade B with 1 finding 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 11d 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
gryph policy test --file ./gryph-policy/<name>.yaml --action command_exec --command "rm -rf /" Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring Gryph Policies
Gryph mediates what an AI coding agent reads, writes, and runs. A policy is an ordered list of rules. Each rule matches an action and returns a decision. This skill helps a human draft those rules, with an agent's help, then hands the human a command to install them.
You draft in a workspace directory. You never install. You never write into Gryph's config directory. The human reviews the draft and runs the install command you give at the end. This keeps the human in control of what becomes active policy.
The two hard rules
- Draft only in a workspace directory you create, for example
./gryph-policy/. Never write a policy file into Gryph's config directory or itspolicies/directory. Gryph blocks an agent write there by design, and a direct write bypasses the human review. - Never install. Do not run
gryph policy install,gryph policy edit, orgryph policy init <name>(a bare name writes intopolicies/). These change live policy. Your job ends at a validated draft plus an install command for the human.
The gryph binary is the source of truth
The installed gryph binary is authoritative and version-matched. Read the schema and
the existing policy from it. Do not author fields from memory.
gryph policy schemaprints the exact rule fields, match criteria, and decision set. This is the single source of truth for the schema. Check it before you write a field.gryph policy builtinprints Gryph's own built-in rules. Read them as working examples to imitate, and to see what already fires so your rule does not collide with them.gryph policy listshows every active source and its rule count.
The security policy guide at https://github.com/safedep/gryph/blob/main/docs/security-policy.md is a concept guide. It explains match criteria, scope, CEL conditions, decisions, messages, receipts, and has worked examples. Read the section you need for concepts. When the doc and the binary disagree, trust the binary and tell the user.
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.
- 11d ago First seen · 142 lines · 200 tokens per session scan B 1621b8b3c0ce
gryph-policy-authoring is a skill published in the GitHub repository safedep/gryph (161 stars, last pushed 11d ago), licensed Apache-2.0. It adds 200 tokens to every session and 1,825 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
mongodb-query-optimizer
Help with MongoDB query optimization and indexing. Use only when the user asks for optimization or performance: "How do I optimize this query?", "How do I index this?", "Why is this query slow?", "Can you fix my slow queries?", "What are the slow queries on my cluster?", etc. Do not invoke for general MongoDB query…
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.
neo4j-modeling-skill
Design, review, and refactor Neo4j graph data models. Use when choosing node labels vs relationship types vs properties, migrating relational/document schemas to graph, detecting anti-patterns (generic labels, supernodes, missing constraints), designing intermediate nodes for n-ary relationships, enforcing schema with…
lov-article-creator
A skill that turns source material or a draft into a complete, branded WeChat public-account article package.
lov-repo2docs
Turn any folder of source material — a code repository, a pile of articles, a mixed knowledge dump with images — into a professional, polished Fumadocs (Next.js) documentation website, then deploy it to https://{product-id}.example.com/docs. Works by reading the folder one unit at a time and incrementally growing and…