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 tacoda/keystone --skill keystone-new-guidegit clone --depth 1 https://github.com/tacoda/keystoneWrote 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-guide)<a href="https://agentmods.dev/skills/tacoda/keystone/keystone-new-guide"><img src="https://agentmods.dev/badge/skills/tacoda/keystone/keystone-new-guide.svg" alt="Measured on agentmods" 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.00015 | $0.00514 |
| Opus 5 | $0.00008 | $0.00257 |
| Sonnet 5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
keystone-new-guide 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 8d 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-guide — scaffold a guide + paired corpus
A guide is a markdown file under .charter/guides/<topic>/
that declares one or more rules (the what); a paired corpus entry
under .charter/corpus/<topic>/ carries the reasoning (the
why). The generator emits both with canonical frontmatter,
charter-root-relative cross-links, and the required tier headings.
Run
keystone new guide <topic>/<name>
Example:
keystone new guide process/release
# writes .charter/guides/process/release.md
# .charter/corpus/process/release.md
Topic selection
The topic directory sets the guide's default activation:
| Topic | Default activation |
|---|---|
domain/ |
Ambient on every action. |
process/ |
On phase entry. |
idioms/<stack>/ |
Lazy by region — only when the touched region's stack matches. |
principles/ |
Ambient on every action. |
computational/ |
Editor / LSP / on-save (tool-driven). |
See docs/ports/guide.md for the
full guide port contract.
After scaffolding
- Fill in the rule body — short, declarative bullets under
## RULES(the default tier). Use## IRON LAW(S)or## GOLDEN RULEonly when warranted. - Fill in the paired corpus body — long-form reasoning, anti-patterns, references.
- Optionally add a
globs:frontmatter list to narrow activation to specific code paths. - Run
keystone indexto refresh the descriptor surface.
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.
- 8d ago First seen · 72 lines · 15 tokens per session scan A 56a4f3cc5562
keystone-new-guide is a skill published in the GitHub repository tacoda/keystone (44 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 514 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.