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-commandgit 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-command)<a href="https://agentmods.dev/skills/tacoda/keystone/keystone-new-command"><img src="https://agentmods.dev/badge/skills/tacoda/keystone/keystone-new-command/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-command"><img src="https://agentmods.dev/badge/skills/tacoda/keystone/keystone-new-command.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.00017 | $0.00358 |
| Opus 5.5 | $0.00007 | $0.00143 |
| Sonnet 5.5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
keystone-new-command 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 1mo 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-command — scaffold a command
An action is one atomic unit of lifecycle work, invoked by name
(by a playbook, another action, the menu file, or the user). Default
actions ship with every install: spec, orient, verify, review,
learn, audit, bootstrap, mode, synthesize, check-drift.
Custom actions for project-specific lifecycle phases live alongside.
Actions live at .charter/actions/<name>.md (flat, no topic
directory — actions are global by name across the cascade).
Run
keystone new command <name>
Example:
keystone new command release-notes
# writes .charter/actions/release-notes.md
After scaffolding
- Fill in
## Entry condition— what must be true before this action runs. - Fill in
## Activities— a numbered list of verb + artifact steps. - Fill in
## Exit condition— what must be true when the action completes. - List dependent sensors / subagents / corpus in the
deps:frontmatter so the indexer can build the graph. - Run
keystone indexto refresh the descriptor surface.
Full port contract:
docs/ports/action.md.
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.
- 1mo ago First seen · 50 lines · 17 tokens per session scan A c8c668add544
keystone-new-command is a skill published in the GitHub repository tacoda/keystone (44 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 358 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…