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 setup_commandsgit 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/setup_commands)<a href="https://agentmods.dev/skills/markmhendrickson/neotoma/setup_commands"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/setup_commands/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/setup_commands"><img src="https://agentmods.dev/badge/skills/markmhendrickson/neotoma/setup_commands.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.00008 | $0.00343 |
| Opus 5.5 | $0.00003 | $0.00137 |
| Sonnet 5.5 | $0.00002 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
setup_commands 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
92% identical to setup-commands — 12 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.
What it actually says
Setup Commands (Legacy)
Foundation workflows have been replaced by skills. There is no longer a foundation/agent_instructions/cursor_commands/ directory; workflows live in foundation/agent_instructions/cursor_skills/{slug}/SKILL.md.
What to do instead
- Use setup-cursor-copies — Run
./foundation/scriptsscripts/setup_claude_instructions.sh.sh(or the setup-cursor-copies skill). It copies foundation rules into.claude/rules/and foundation skills into.cursor/skills/. - Load skills by trigger — When a trigger matches (e.g. commit, pull, push, fix-feature-bug), load the corresponding skill from
.cursor/skills/{slug}/SKILL.mdper the router rule.
When this skill is invoked
- Tell the user that foundation no longer installs into
.claude/skills/. - Run or direct them to run setup-cursor-copies to refresh
.claude/rules/and.cursor/skills/. - Repository-specific command files in
docs/*_command.md(if any) may still be installed by setup into.claude/skills/when configured in the manifest; foundation workflows are only in.cursor/skills/.
Related
- setup-cursor-copies skill — Copies foundation rules and skills into
.cursor/. - Foundation skills source:
foundation/agent_instructions/cursor_skills/
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 · 28 lines · 8 tokens per session scan A e0d23ff5fde1
setup_commands is a skill published in the GitHub repository markmhendrickson/neotoma (34 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 343 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to setup-commands, differing in 12 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.