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/releasenpx skills add markmhendrickson/neotoma --skill 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/release)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/release"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/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.00003 | $0.08905 |
| Opus 5 | $0.00002 | $0.04452 |
| Sonnet 5 | $0.00001 | $0.01781 |
| Haiku 4.5 | $0.00000 | $0.00890 |
Grade C, and why
release scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl -fsS -H "Accept: application/json" https://sandbox.neotoma.io/ | node -e 'let s="";process.stdin.on("data",d=>s+=d).on("end",()=>{const j=JSON.parse(s); if (j.version !== "X.Y.Z" || j.mode !== "sandbox") { console.e Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsS -H "Accept: application/json" https://sandbox.neotoma.io/ | node -e 'let s="";process.stdin.on("data",d=>s+=d).on("end",()=>{const j=JSON.parse(s); if (j.version !== "X.Y.Z" || j.mode !== "sandbox") { console.e How it starts
The opening of the file, as written. The whole thing — 506 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Prepare and ship a GitHub + npm + sandbox release with a mandatory preview step. A confirmed execute run is not complete until npm publish succeeds from the published package root and sandbox.neotoma.io is deployed and verified, unless the user explicitly scoped the request to GitHub-only / no registry / no sandbox.
When to Use
When you want to ship what is on dev (or the current integration branch) to main, tag it, publish to npm, create a GitHub Release with curated notes, and update the public sandbox deployment.
Trigger with /release, or naturally ("prepare a release", "let's ship v0.5.0").
Reference Documents
| Document | Role |
|---|---|
docs/developer/github_release_process.md |
GitHub Release template layout, release-notes:render usage, gh release create |
docs/developer/github_release_supplement.example.md |
Section pattern for the human-readable supplement |
docs/infrastructure/deployment.md |
Sandbox Fly deployment command and verification |
docs/subsystems/sandbox_deployment.md |
Sandbox runtime behavior and operator runbook |
.github/release_notes_wrap.md |
Fixed wrap template (install commands, npm/compare table, commit list) |
Workflow
Step 1: Preflight
Run before anything else:
- Fetch:
git fetch origin(and other configured remotes). - Determine branches: Default integration =
dev, target =main. Override if the user specifies. - Commits not on main:
git log origin/main..origin/dev --oneline(ororigin/main..HEADon integration branch). This is the default scope of "what ships." - Uncommitted changes:
git status --short. If dirty, describe the actual pending work grouped by area/impact usinggit diff --statand targeted file inspection. Do not use a generic placeholder. - Submodules:
git submodule status— surface any that are ahead/behind recorded SHAs. - Previous tag:
git tag --sort=-v:refname | head -1— this is the compare base unless the user specifies--compare-base. - Current package.json version: Read and display.
- Existing GitHub Release check: Run
gh release view "vX.Y.Z" --json isDraft,tagName 2>/dev/nullfor the target version. If a release exists and is a draft, surface this to the user ("Draft release vX.Y.Z already exists on GitHub — execute will update it rather than create a new one."). If a release exists and is not a draft (already published), STOP and ask the user explicitly before proceeding — updating a published release's notes is a hold point. - Sandbox deploy readiness: Confirm
fly.sandbox.tomlexists,flyctlis available, and the active Fly account can deployneotoma-sandbox. If Fly auth is missing, report that execute will block at sandbox deployment unless the user explicitly scopes the release to no sandbox.
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 · 506 lines · 3 tokens per session scan C 0046729168ed
release is a skill published in the GitHub repository markmhendrickson/neotoma (31 stars, last pushed yesterday), licensed MIT. It adds 3 tokens to every session and 8,905 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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…