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/draft-comparative-neotoma-post/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/draft-comparative-neotoma-post)<a href="https://agentmods.dev/skills/markmhendrickson/ateles/draft-comparative-neotoma-post"><img src="https://agentmods.dev/badge/skills/markmhendrickson/ateles/draft-comparative-neotoma-post.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.1 | $0.00076 | $0.01201 |
| Opus 5 | $0.00038 | $0.00600 |
| Sonnet 5 | $0.00015 | $0.00240 |
| Haiku 4.5 | $0.00008 | $0.00120 |
Grade A, and why
draft-comparative-neotoma-post 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 6d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Comparative Neotoma Post
Draft a post in the memory & truth-layer series: it compares a specific product or API's memory (e.g. Claude Memory Tool, OpenAI API, ChatGPT Memory, Claude app Memory) to a truth layer and explains when each fits. The format is flexible so posts stay consistent without sounding cookie-cutter.
Source of truth for format
Always use the format defined in the posts README. Before drafting or editing, read:
execution/website/markmhendrickson/react-app/src/content/posts/README.md — section "Format: memory & truth-layer series".
That section defines the recurring beats and how to avoid cookie-cutter repetition. Do not duplicate the full format here; the README is the single source of truth.
When to use this skill
- User asks to draft a new post comparing [Product/API] memory to a truth layer (e.g. "draft a memory series post for Gemini").
- User asks to edit or extend an existing comparative Neotoma post and you need the series format in context.
- User says "comparative neotoma post", "memory series post", or "truth layer comparison post" in the context of writing.
Workflow
-
Resolve slug and scope
- If user named a product/API (e.g. Gemini, OpenAI API, ChatGPT), derive a slug (e.g.
gemini-memory-and-truth-layer,openai-api-memory-and-truth-layer). Use lowercase, hyphens, no special characters. - If editing an existing draft, use its slug from
execution/website/markmhendrickson/react-app/src/content/posts/drafts/.
- If user named a product/API (e.g. Gemini, OpenAI API, ChatGPT), derive a slug (e.g.
-
Load format
- Read the README section "Format: memory & truth-layer series" (recurring beats, how to avoid cookie-cutter).
- Apply it to the specific product/API: choose section titles that fit (e.g. "What's missing" vs "Where it falls short"), include optional sections (e.g. "How configuration works" for developer posts, comparison table when it adds clarity).
-
Draft the post
- Create or edit
execution/website/markmhendrickson/react-app/src/content/posts/drafts/{slug}.md. - Include YAML frontmatter:
title,excerpt. - Follow the beats: opening (what it is + scope), what it is, where it excels, where it falls short, when a truth layer makes sense, optional config/FAQ, what I'm building (Neotoma paragraph).
- Link to
/posts/truth-layer-agent-memoryand to other series posts where relevant (e.g. Claude developer post, ChatGPT Memory post). - Keep voice consistent; use product-specific examples and avoid filler phrases repeated verbatim.
- Create or edit
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.
- 6d ago First seen · 73 lines · 76 tokens per session scan A 7b5240d3c8f1
draft-comparative-neotoma-post is a skill published in the GitHub repository markmhendrickson/ateles (6 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 1,201 once invoked, about $0.0004 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-31.
Other skills, from other repositories
local-llm-tool
Local LLM execution tool for text generation and chat through Ollama or vLLM endpoints. Use when: running on-prem inference, calling a local GPU model, or summarizing with a self-hosted LLM.
colm
COLM (Conference on Language Modeling) paper formatting — activate when the user wants COLM template setup, migration, or formatting/compilation fixes.
aaai
AAAI paper formatting — activate when the user wants AAAI template setup, migration, or formatting/compilation fixes.
conference-research
Academic venue paper discovery — activate when you need to find papers accepted at specific conferences or journals (ACL, EMNLP, NeurIPS, ICML, ICLR, MLSys, etc.), analyze venue acceptance preferences, or look up CFP requirements.
understand-codebase
Understand an unfamiliar codebase or plan a change safely, using Spine's deterministic knowledge-graph MCP tools. Reach for this before answering structural questions about a repo you don't know, before editing code, or when debugging — it hands you engineering decisions (what a change breaks, what's untested, where a…
tasks
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.