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/pullnpx skills add markmhendrickson/neotoma --skill pullgit clone --depth 1 https://github.com/markmhendrickson/neotomaWhat 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.02419 |
| Opus 5 | $0.00002 | $0.01210 |
| Sonnet 5 | $0.00001 | $0.00484 |
| Haiku 4.5 | $0.00000 | $0.00242 |
Grade A, and why
pull 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 3d 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
1 near-identical copy found in the catalogue:
- pull — 95% identical, 7 lines differ
How it starts
The opening of the file, as written. The whole thing — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: pull description: Pull from origin; supports /pull . triggers:
- pull
- /pull
pull
Pull latest commits from origin, committing local changes first, merging conflicts, and running setup scripts.
SUBMODULE MODE: If a submodule name is provided (e.g., /pull foundation), scope operations to that submodule only, not the main repository.
Configuration is read from foundation-config.yaml.
If submodule name provided:
- Check if submodule exists:
git submodule status <submodule-name> - Change to submodule directory:
cd <submodule-name> - Run pull workflow in submodule context
- Exit after submodule pull (do NOT pull main repository)
If no submodule name provided, proceed with main repository pull workflow below.
Workflow Overview
- Commit local changes using foundation commit command (if any uncommitted changes)
- Fetch latest from origin
- Pull latest commits (merge or rebase based on configuration)
- Resolve merge conflicts if they occur
- Run setup scripts as needed
Tasks
Step 1: Determine Scope
If submodule name provided:
-
Verify submodule exists:
if ! git submodule status <submodule-name> >/dev/null 2>&1; then echo "❌ Submodule not found: <submodule-name>" exit 1 fi -
Save parent directory and change to submodule directory:
ORIGINAL_DIR=$(pwd) # Save parent directory before cd cd <submodule-name> || exit 1 -
Update scope context (all subsequent operations in submodule)
If no submodule name provided, proceed with main repository context.
Step 2: Check for Uncommitted Changes
# Check if there are uncommitted changes
if git status --porcelain | grep -q .; then
echo "📝 Found uncommitted changes, committing first..."
# Use foundation commit command to commit changes
# Agent should invoke the commit command workflow:
# - Run security audit
# - Stage changes
# - Generate commit message
# - Commit changes
# - Push to origin if configured
# For agent: Use the foundation commit command workflow
# Invoke: `/commit <submodule-name>` (if submodule) or `/commit` (if main repo)
echo "✅ Local changes committed"
else
echo "✅ No uncommitted changes"
fi
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.
- 3d ago First seen · 323 lines · 3 tokens per session scan A e5f3134ac4c4
pull is a skill published in the GitHub repository markmhendrickson/neotoma (29 stars, last pushed 6d ago), licensed MIT. It adds 3 tokens to every session and 2,419 once invoked, about $0.0000 per session on Opus 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
bilibili_search
Search for videos on Bilibili using keyword queries generated from user interests.
writing-specs
Use when authoring a spec or implementation plan, or planning multi-task work.
release
Use when releasing a version, bumping project versions, or pushing release tags.
add-platform-source
Use when adding, integrating, repairing, hardening, completing, auditing, testing, or releasing an OpenBiliClaw platform/source adapter, including anonymous or credentialed APIs, browser-extension tasks and identity, source auth/status, bootstrap and incremental sync, formal discover, configuration, recommendation…
comment_analysis
Analyze video comment sections to discover recommended content and gauge content quality.
spec
Spec-driven development orchestrator. The single entry point for all spec work: creating features, fixing bugs, evolving APIs. Drives the full 6-step pipeline (spec → RED tests → implement → GREEN tests → validate → update docs) autonomously, only pausing for developer approval at gate points. Use when asked to 'add a…