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 markmhendrickson/neotoma --skill create-plangit clone --depth 1 https://github.com/markmhendrickson/neotomaWrote 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/markmhendrickson/neotoma/create-plan)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/create-plan"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/create-plan/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/markmhendrickson/neotoma/create-plan"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/create-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Agent Snooping · line 6 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00006 | $0.00715 |
| Opus 5.5 | $0.00002 | $0.00286 |
| Sonnet 5.5 | $0.00001 | $0.00143 |
| Haiku 4.5 | $0.00001 | $0.00072 |
Grade A, and why
create-plan 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- create-plan — 95% identical, 9 lines differ
- create_plan — 94% identical, 13 lines differ
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: create-plan description: Create a new plan as a Neotoma entity, optionally linked to objectives, releases, or other plans. triggers:
- create plan
- new plan
- create a plan
- /create-plan
Create New Plan
Create a new plan entity in Neotoma with title = {{input:title}}.
Follow the complete workflow in foundation/development/plan_workflow.md. Configuration is read from foundation-config.yaml.
This workflow can also be triggered automatically via .claude/rules/plan_detection.mdc when you mention planning-related patterns in natural language (e.g., "create plan", "new plan"). Both paths execute the same workflow.
Workflow Overview
Implements Checkpoint 0 of the plan creation workflow:
- Collect required plan fields from the user
- Run alignment check (summary → user confirms)
- Store plan as a Neotoma
planentity - Create relationships to related entities
- Optionally rebuild the
neotoma-plansmirror
Tasks
-
Collect required fields:
Ask the user for any missing required fields:
title— Short, imperative namedescription— Problem being solved and why it mattersscope— What is explicitly in scopeout_of_scope— What is explicitly out of scopesuccess_criteria— Measurable conditions for completionstatus— Default todraft
Optional fields to offer (collect if relevant):
priority(P0/P1/P2/P3)phasetarget_releasedeliverablesdependencies(canonical names of plans this plan requires)testing_notesobservability_notes
-
Alignment check:
After collecting fields, produce a concise summary:
- Problem it solves and why it exists
- What is explicitly in scope and out of scope
- Critical constraints or invariants
Ask: "Does this accurately capture what you want this plan to do?"
Incorporate corrections and re-summarize if changes are substantial. Do not proceed until the user confirms.
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 · 100 lines · 6 tokens per session scan A c4f462cd1432
create-plan is a skill published in the GitHub repository markmhendrickson/neotoma (34 stars, last pushed 2d ago), licensed MIT. It adds 6 tokens to every session and 715 once invoked, about $0.0000 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-08-30.
Other skills, from other repositories
akf-trust-metadata
The AI native file format. EXIF for AI — stamps every file with trust scores, source provenance, and compliance metadata. Embeds into 20+ formats (DOCX, PDF, images, code). EU AI Act, SOX, HIPAA auditing.
bilibili_search
Search for videos on Bilibili using keyword queries generated from user interests.
bernstein-plan
Create and manage multi-step execution plans in Bernstein. Plans decompose complex goals into stages with dependencies. Use when the user wants to plan a complex feature, break down a large task, or review an execution plan before agents start working.
bernstein-run
Run a verified multi-agent goal with Bernstein. Use when a task is too large for a single agent session: Bernstein decomposes the goal into tasks, spawns CLI coding agents in parallel git worktrees, verifies their output, and merges results. Also use to check run status, costs, and to verify a finished run against its…
taste-explorer
A guided interview skill that asks focused questions to learn what a person likes and dislikes, then saves confirmed preferences as long-term memory.
bernstein-approve
Review and approve/reject pending tasks or plans in Bernstein. Use when the user asks about approvals, wants to review agent work, or needs to approve/reject a plan before execution begins.