Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tacoda/keystonenpx agentmods add skills/tacoda/keystone/keystone-new-policyWrote 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/tacoda/keystone/keystone-new-policy)<a href="https://agentmods.dev/skills/tacoda/keystone/keystone-new-policy"><img src="https://agentmods.dev/badge/skills/tacoda/keystone/keystone-new-policy/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/tacoda/keystone/keystone-new-policy"><img src="https://agentmods.dev/badge/skills/tacoda/keystone/keystone-new-policy.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.00012 | $0.00387 |
| Opus 5 | $0.00006 | $0.00193 |
| Sonnet 5 | $0.00002 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
keystone-new-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 10d 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.
What it actually says
keystone:new-policy — scaffold a policy repo
A policy is a separately-versioned charter fragment that consumer
projects pin in their keystone.json (e.g. an org-wide policy that
ships strict guides). This generator writes a fresh policy repo
skeleton — manifest, charter directory layout, README — that you then
populate and publish.
Unlike the other generators, keystone new policy writes to
./<name>/ in the current working directory, not into an existing
charter install.
Run
From the directory where the policy repo should land:
keystone new policy <name>
Example:
keystone new policy acme-policies
# writes ./acme-policies/{keystone-policy.json, .charter/, README.md, ...}
After scaffolding
- Fill in
keystone-policy.json— name, version, required port declarations, strict locks. - Author the policy's
.charter/content — guides, sensors, etc. - Initialize git and push to a host so consumers can pin the source.
- Consumers add the policy via
keystone policy add <owner>/<repo>@<version>.
See the policy authoring guide for the full policy lifecycle.
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.
- 10d ago First seen · 61 lines · 12 tokens per session scan A 41adbe79ab26
keystone-new-policy is a skill published in the GitHub repository tacoda/keystone (44 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 387 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-30.
Other skills, from other repositories
portaljs-new-portal
Scaffold a new PortalJS data portal from a brief. Copies the canonical template from examples/portaljs-catalog and substitutes project tokens. Use when starting a brand-new data portal project from scratch.
workflow-creation
Create a new Stencila workflow. Use when asked to create, write, scaffold, or set up a workflow directory or WORKFLOW.md file. Covers workflow discovery, duplicate-name checks, ephemeral workflows, WORKFLOW.md frontmatter, DOT pipeline authoring, goals, agents, branching, composition, and validation.
agent-creation
Create a new Stencila agent. Use when asked to create, write, scaffold, or set up an agent directory or AGENT.md file. Covers workspace and user-level agents with model, provider, tool, trust, and MCP configuration.
skill-creation
Create a new Stencila workspace skill. Use when asked to create, write, or scaffold a SKILL.md file or skill directory.
design-import
Scaffolds React components from a Claude Design handoff bundle and stops at files on disk: no stories, no tests, no pull request. Use when handed a claude.ai/design URL or a local bundle file; when that same scaffold should carry on through test generation, browser verification and an opened PR, run /ork:design-ship…
plugin-init
A project starter for creating Zhin.js plugins, which are installable packages that extend the Zhin.js bot framework. It sets up the required files, folders, package metadata, entry point, and documentation.