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 publish_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/publish_plan)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/publish_plan"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/publish_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/publish_plan"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/publish_plan.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.00005 | $0.01440 |
| Opus 5.5 | $0.00002 | $0.00576 |
| Sonnet 5.5 | $0.00001 | $0.00288 |
| Haiku 4.5 | $0.00001 | $0.00144 |
Grade A, and why
publish_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.
This is a copy
94% identical to publish-plan — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
publish-plan
Convert a plan file (release plan, feature spec, or .cursor/plans/ file) into a
GitHub Discussion post written for external readers. Strips internal references and
PII, rewrites for a public audience, and optionally posts via the GitHub CLI.
When to Use
Use when you have a plan in progress and want external input before execution. Pass the path to any plan document as the argument:
/publish-plan docs/releases/in_progress/v0.12.0/release_plan.md
/publish-plan .cursor/plans/some_plan.md
/publish-plan docs/feature_units/in_progress/FU-2026-01-001/FU-2026-01-001_spec.md
Optionally pass a specific question to ask readers as a second argument:
/publish-plan docs/releases/in_progress/v0.12.0/release_plan.md "Does this sync model work for your use case?"
Step 1: Read and Parse the Plan
- Read the plan file at the provided path.
- Extract the following from the document:
- Goal / motivation: Why does this exist? What problem does it solve?
- Approach / key decisions: What choices were made or are still open?
- Scope boundaries: What is explicitly excluded or deferred?
- Open questions: What is uncertain or unresolved?
Step 2: Strip Internal References
Remove or redact anything that should not be public:
- Full names and email addresses of individuals
- Internal Slack channels, ticket numbers, or system identifiers that leak org structure
- Pricing, cost, or revenue figures
- Internal hostnames, credentials, or environment-specific configuration values
- Agent execution notes (batch status, orchestrator output, FU dependency trees)
- Anything marked
<!-- internal -->or[INTERNAL]
Do not strip:
- Feature IDs (FU-YYYY-MM-NNN) — these are useful public references
- Architecture decisions and technical rationale
- Version numbers and release IDs
- Links to public repo files or issues
Step 3: Draft the Discussion Post
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 · 210 lines · 5 tokens per session scan A 1197a1a82500
publish_plan is a skill published in the GitHub repository markmhendrickson/neotoma (34 stars, last pushed 2d ago), licensed MIT. It adds 5 tokens to every session and 1,440 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to publish-plan, differing in 13 lines, and is treated as a copy.
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.