Borrowing it
Nothing to install: this file belongs to markmhendrickson/ateles. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/markmhendrickson/ateles/main/.claude/skills/store-neotoma/SKILL.mdgit clone --depth 1 https://github.com/markmhendrickson/atelesWrote 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/ateles/store-neotoma)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/store-neotoma"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/store-neotoma/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/ateles/store-neotoma"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/store-neotoma.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.00069 | $0.02493 |
| Opus 5 | $0.00034 | $0.01247 |
| Sonnet 5 | $0.00014 | $0.00499 |
| Haiku 4.5 | $0.00007 | $0.00249 |
Grade A, and why
store-neotoma 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
store-neotoma
Purpose
Define the workflow for reviewing chat and storing it in Neotoma — conversation, dual agent_message rows per turn, derived transcript + analysis, and attachments — then reporting a succinct affected-records list. Neotoma is the only data store; there is no Parquet migration phase.
Execution policy (no confirmation gate)
/store_neotoma stores directly, then reports — it does NOT preview-and-wait. (Updated 2026-06-05 per operator: the prior mandatory preview/confirm gate is removed, matching /end.) Build the plan, execute the store, then render the affected-records summary. The user may still steer: if the user volunteers scope or "how to store" input (in their invocation or a follow-up), apply it; if they explicitly ask to see a preview first, honor that one-off request. Absent such input, do not block on confirmation.
Scope
Applies when the user asks to store the current chat in Neotoma. Covers extraction, storage, relationships, and reporting. Stores conversation, two agent_message entities per logical turn (role: "user" and role: "assistant"), each with PART_OF → conversation — the canonical shape from Neotoma MCP live chat instructions — plus derived transcript and analysis synthesized from whatever the conversation actually provides (see below), plus attachments.
Prerequisites
- Chat transcript available in agent context (user and agent messages).
- Neotoma MCP available.
- Load
.cursor/rules/conversation_tracking.mdcand.cursor/rules/neotoma_harness.mdcfor entity schemas and access rules.conversation_trackingdefines dual-message +PART_OF; do not use mergedrole_user/role_agenton a singleagent_message.
Phase 0: Extraction (build the store plan)
Step 0.1 — Extract
Parse all user and agent messages in the conversation. For each logical turn (user message + following assistant reply):
- User row:
entity_type: agent_message,role: "user",content= exact user text,turn_key(stable per turn), optionalturn_number(1-based),timestamp,files_modified,tools_used,platform,model,neotoma_operations(inferred from the turn). - Assistant row:
entity_type: agent_message,role: "assistant",content= exact assistant text shown in chat,turn_keye.g. same base +:assistant, optional sameturn_number/timestampfor sorting. - Topics: extract from user questions, entity types discussed, file paths, domain keywords (finance, admin, health, work).
- Decisions: extract when agent states an approach, user confirms a choice, or implementation strategy is chosen.
- Action items: tasks to create, follow-ups mentioned.
files_modified: file paths from tool calls, @-mentions, or explicit file references (typically attributed to the user message for that turn).neotoma_operations: inferred from agent tool-call patterns (store,correct,create_relationship).
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.
- 5d ago First seen · 125 lines · 69 tokens per session scan A d2be17c83cb4
store-neotoma is a skill published in the GitHub repository markmhendrickson/ateles (6 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 2,493 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
cvpr-iccv-eccv
CVPR / ICCV / ECCV paper formatting — activate when the user wants to submit to CVPR, ICCV, or ECCV, follow their template, or fix format issues for these computer vision conferences.
figure-drawing
MANDATORY skill for creating any figure, diagram, chart, table visualization, or TikZ graphic in a paper. Must be activated BEFORE writing any drawing code. Produces standalone .tex → compiled PDF/PNG → \includegraphics in paper. Never inline TikZ code directly into paper sections.
paper-research-form
A workflow for collecting and comparing research papers in a structured CSV file. A literature review is a selected summary of existing research on a topic.
user-preview
Compile the current project's LaTeX files and send the generated PDF to the user for preview. Use when the user wants to check typesetting results or confirm the effect of recent edits.
nano-pdf
Edit PDFs with natural-language instructions using the nano-pdf CLI.
notion
Notion API for creating and managing pages, databases, and blocks.