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 agentmods add skills/markmhendrickson/neotoma/create_releasenpx skills add markmhendrickson/neotoma --skill create_releasegit 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_release)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/create_release"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/create_release.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 | $0.00006 | $0.03946 |
| Opus 5 | $0.00003 | $0.01973 |
| Sonnet 5 | $0.00001 | $0.00789 |
| Haiku 4.5 | $0.00001 | $0.00395 |
Grade A, and why
create_release 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 4d 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
95% identical to create-release — 14 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 — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create New Release
Orchestrates multiple Feature Units into a cohesive release. Implements the Release workflow from foundation/development/release_workflow.md.
When to Use
Explicit Command: Use when you know exactly what you want: start a new release, plan multi-FU work with dependency resolution, generate execution schedules with parallelization, orchestrate FU creation/execution in dependency order, run cross-FU integration tests.
Automatic Detection: This workflow can also be triggered automatically via .claude/rules/release_detection.md when you mention release-related patterns in natural language (e.g., "new release", "release v1.1.0"). Both paths execute the same workflow.
This is a foundation command. If installed, it will be available in .claude/skills/ via symlink.
Prerequisites
- Release ID chosen (format:
vX.Y.Z, e.g.,v1.0.0) - Release scope roughly defined (what's in, what's out)
- FU IDs for included work identified (or to be created)
Command Execution
Step 1: Load Documentation
Load required documents:
foundation/development/release_workflow.md(primary workflow)docs/feature_units/standards/creating_feature_units.md(FU creation)docs/feature_units/standards/execution_instructions.md(FU execution)docs/feature_units/completed/anddocs/feature_units/in_progress/(for Feature Unit specs)
Step 2: Checkpoint 0 — Release Planning
Check if Release plan exists:
- Look for
docs/releases/in_progress/{release_id}/release_plan.md - Look for
docs/releases/in_progress/{release_id}/manifest.yaml
If Release plan exists: Load and validate. If complete → proceed to Step 3. If incomplete → prompt user to complete.
If Release plan does NOT exist: Prompt user interactively for Release details:
- Release name and version (e.g., "MVP", "v1.0.0")
- Release goal (1-2 sentence summary of what this ships)
- Target ship date (date or "when ready")
- Priority (P0 critical / P1 high / P2 normal)
- Included Feature Units (list of FU IDs, e.g., "FU-100, FU-101, FU-102")
- Excluded scope (what's explicitly NOT in this release)
- Release-level acceptance criteria:
- Product acceptance (core workflows, empty/error states)
- Technical acceptance (test coverage, performance, integrity)
- Business acceptance (metrics, KPIs)
- Cross-FU integration test requirements (flows that span multiple FUs)
- Deployment strategy (staging_first / canary / full_rollout)
- Rollback plan (how to revert if issues found)
- Post-release monitoring plan (key metrics, alerts)
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.
- 4d ago First seen · 442 lines · 6 tokens per session scan A 90fad2af8dd9
create_release is a skill published in the GitHub repository markmhendrickson/neotoma (31 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 3,946 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to create-release, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
security-observability
只读查询 agent-sec-cli 已落盘的历史安全事件记录，并据此生成会话级安全复盘。仅当用户显式要求查看或审计已发生的安全事件、安全告警、安全审计记录，或要求按 session/run/trace/时间/类别筛选与统计已有安全事件，或要求复盘某次会话的安全判定时使用。不用于扫描新内容：检查代码安全性用 code-scanner，检测 prompt 注入用 prompt-scanner，审查 Skill 安全状态用 skill-ledger。不要因为对话中出现“安全”“工具调用”等字样、或为了主动自查而触发。.
add-backend
Guide for adding a backend (Rust or Python) to the agent-sec-core security middleware. Use when creating new backends, integrating Rust or Python code into the security middleware, or extending with new backend actions.
skill-ledger
Skill 安全状态查看、风险暴露审查、用户决策、快速扫描认证与可选深度扫描。支持用户主动查看或扫描单个/全部 Skill；当用户要求 agent 安装 Skill 且安装成功后，必须自动对最终本地目录执行快速扫描认证。.
pr-body
分析当前分支的全部变更，自动生成或更新 PR 标题和正文。聚焦内容质量：解释 why、归纳 what、标注测试方式，遵循 anolisa 项目 PR 模板规范。适用于新建 PR 前生成描述，或已有 PR 需要更新描述。.
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.
install-openclaw
Install and configure OpenClaw non-interactively with Alibaba Cloud Model Studio. Use when the user asks to install OpenClaw, configure Aliyun Bailian/Model Studio/DashScope credentials, choose pay-as-you-go, Coding Plan, or Token Plan billing, set Base URL/model config, optionally configure DingTalk, start the local…