Borrowing it
Nothing to install: this file belongs to dogwood-policy/dogwood. 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/dogwood-policy/dogwood/main/.claude/skills/authoring-action-schema/SKILL.mdgit clone --depth 1 https://github.com/dogwood-policy/dogwoodWrote 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/dogwood-policy/dogwood/authoring-action-schema)<a href="https://agentmods.dev/skills/dogwood-policy/dogwood/authoring-action-schema"><img src="https://agentmods.dev/badge/skills/dogwood-policy/dogwood/authoring-action-schema/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/dogwood-policy/dogwood/authoring-action-schema"><img src="https://agentmods.dev/badge/skills/dogwood-policy/dogwood/authoring-action-schema.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00190 | $0.03270 |
| Opus 5 | $0.00095 | $0.01635 |
| Sonnet 5 | $0.00038 | $0.00654 |
| Haiku 4.5 | $0.00019 | $0.00327 |
Grade A, and why
authoring-action-schema 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 13d 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.
How it starts
The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring the Cedar action schema for a Dogwood deployment
Your job: produce the action schema — a Cedar .cedarschema — that declares
the world a Dogwood deployment governs: its entity types (the principals and
resources), one action per tool/operation, and each action's context
laid out as input / output / system. This schema is the foundation every
policy scopes over, so it comes first in the lifecycle: an action schema is
required before you declare a service schema and before you write any policy.
This is a modeling task. The syntax is plain Cedar and fully documented (see
Ground truth) — the hard part is
deciding what your world looks like: which entities are principals vs
resources, what counts as one action, and which fields belong under input vs
output vs system. You also choose how to produce the file: hand-write it,
or generate it from an MCP tools/list manifest.
Do not invent Cedar schema syntax from memory, and do not return a
schema you have not checked with the dogwood CLI. Follow the loop below in
order:
- Decide the shape — resolve the modeling questions, and pick hand-write vs MCP-generate (Step 1).
- Author or generate the
.cedarschema(Step 2). - Check it — run
dogwood schema actionand fix until it exits0; this is mandatory (Step 3). - Hand off — present the schema and point at the next lifecycle skill (Step 4).
The ground truth (read before authoring)
The action schema is standard Cedar .cedarschema — Dogwood adds no schema
syntax, only a convention for the context record. Treat these docs as
authoritative; do not guess. Paths are relative to this skill directory
(.claude/skills/authoring-action-schema/); the guide lives in the
dogwood-docs crate:
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.
- 13d ago First seen · 251 lines · 190 tokens per session scan A 66bffbf8a719
authoring-action-schema is a skill published in the GitHub repository dogwood-policy/dogwood (384 stars, last pushed today), licensed Apache-2.0. It adds 190 tokens to every session and 3,270 once invoked, about $0.0010 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…